Create a Bitcoin withdrawal QR code
AI agents use create-withdrawal-request to create or update resources in ZBD MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your ZBD MCP Server environment.
An AI agent can call create-withdrawal-request faster than any human can review — one bad instruction and it creates or modifies resources in ZBD MCP Server by the hundred, each call as confident as the last.
Attacks that exploit this kind of access
Create a Bitcoin withdrawal QR code. It is categorised as a Write tool in the ZBD MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the ZBD MCP Server MCP server in PolicyLayer and add a rule for create-withdrawal-request: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches ZBD MCP Server. Nothing to install.
create-withdrawal-request is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the create-withdrawal-request rule in your PolicyLayer policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.
Set action: deny in the PolicyLayer policy for create-withdrawal-request. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.
create-withdrawal-request is provided by the ZBD MCP Server MCP server (zbdpay/zbd-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.