AI agents use send_paypal to commit financial operations through ClawPay — usually the final step of a payment, billing, or trading workflow. A call moves real money.
Sending money via PayPal Payouts commits financial obligations and moves funds irreversibly from one account to another. This is the most severe category (Financial > Destructive > Execute > Write > Read). An AI agent with access to this tool could drain accounts, send unauthorized payments, or commit fraud.
From the tool's definition Tool description states 'Send money via PayPal Payouts to an email address or phone number' — a direct money transfer operation. Server context confirms this is a payment processor integration.
Attacks that exploit this kind of access
Send money via PayPal Payouts to an email address or phone number. It is categorised as a Financial tool in the ClawPay MCP Server, which means it involves financial transactions. Block by default and require explicit approval.
Register the ClawPay MCP server in PolicyLayer and add a rule for send_paypal: 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 ClawPay. Nothing to install.
send_paypal 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_paypal 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_paypal. 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_paypal is provided by the ClawPay MCP server (xodn348/clawpay). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →