AI agents use setup_paypal to commit financial operations through ClawPay — usually the final step of a payment, billing, or trading workflow. A call moves real money.
This tool configures and links a PayPal account to the system. While it is primarily a setup/write operation, it establishes financial account credentials that enable subsequent payment operations (pay, send_paypal, refund) on the ClawPay server. Misconfiguration or misuse could link an attacker-controlled PayPal account or expose financial credentials, making it a Financial-category risk.
From the tool's definition Link PayPal account using Client ID and Client Secret... PAYPAL_CLIENT_ID and PAYPAL_CLIENT_SECRET
Attacks that exploit this kind of access
Link PayPal account using Client ID and Client Secret. Reads credentials from PAYPAL_CLIENT_ID and PAYPAL_CLIENT_SECRET environment variables or config file. 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 setup_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.
setup_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 setup_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 setup_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.
setup_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 →