AI agents use send_email_payments to commit financial operations through Zbd — usually the final step of a payment, billing, or trading workflow. A call moves real money.
This tool moves real money (Bitcoin payments) to arbitrary email addresses. Misuse could result in irreversible financial losses. Financial is the highest severity category and clearly applies here.
From the tool's definition Send instant Bitcoin payments to any email
Attacks that exploit this kind of access
Send instant Bitcoin payments to any email. It is categorised as a Financial tool in the Zbd MCP Server, which means it involves financial transactions. Block by default and require explicit approval.
Register the Zbd MCP server in PolicyLayer and add a rule for send_email_payments: 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. Nothing to install.
send_email_payments is a Financial tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the send_email_payments 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 send_email_payments. 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.
send_email_payments is provided by the Zbd MCP server (zebedeeio/zbd-payments-typescript-sdk). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
send_email_payments is one line of Zbd's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →