Zambo guide
MCP Tool Poisoning
Tool poisoning is when an MCP server’s tool description carries hidden instructions for your agent; here is how to spot it and what to record when it happens.
Add Zambo to your AIWhat tool poisoning is
Use records as supporting material, then map each record to the requirement you are reviewing. Keep the controlling source text, the system scope, access rules and retention policy available to the reviewer.
This is operational guidance, not a legal conclusion. A receipt does not establish compliance by itself. Check the current primary source and ask qualified counsel about your situation.
A two-minute check
Apply MCP tool poisoning to one concrete task. Keep the requested action, the returned result and the material used to review it together, then label anything that was not checked.
Record the evidence
For MCP tool poisoning, capture the request, the action taken and the result while the work is fresh. Keep the original request beside the record so a reviewer can compare what was asked with what returned.
Include only details needed to understand this task.
Try this prompt
Start with a small request. Change the details to match your task.
Use Zambo to help with MCP tool poisoning. Show the steps you actually ran and give me a link I can review.
FAQ
What is MCP tool poisoning?
Tool poisoning is when an MCP server’s tool description carries hidden instructions for your agent; here is how to spot it and what to record when it happens.
What does a Zambo receipt show?
It shows the saved record and its available status. It does not prove that the output is correct or complete.
How do I try this with Zambo?
Add Zambo to a supported AI app from /add, ask it to use Zambo for the task, then open the returned receipt link.
Try it with your AI
Connect Zambo once, then ask your AI to use it for a real task.
Add Zambo to your AI Try Zambo Chat