Accept a pending payment request. This will send the requested amount to the requester.
AI agents use cashapp_accept_request to commit financial operations through Mcp Cashapp — usually the final step of a payment, billing, or trading workflow. A call moves real money.
This tool directly moves money by sending a payment to a requester. It commits a financial transaction that transfers funds from the user's Cash App account. Misuse by an AI agent could result in unauthorized payments being sent, making it Financial category with critical severity due to direct monetary impact.
From the tool's definition Accept a pending payment request. This will send the requested amount to the requester.
Attacks that exploit this kind of access
Accept a pending payment request. This will send the requested amount to the requester. It is categorised as a Financial tool in the Mcp Cashapp MCP Server, which means it involves financial transactions. Block by default and require explicit approval.
Register the Mcp Cashapp MCP server in PolicyLayer and add a rule for cashapp_accept_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 Mcp Cashapp. Nothing to install.
cashapp_accept_request 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 cashapp_accept_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 cashapp_accept_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.
cashapp_accept_request is provided by the Mcp Cashapp MCP server (markswendsen-code/mcp-cashapp). 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 →