Process refund via Stripe. Requests user authorization, then sends mandate to Stripe.
AI agents use process_refund to commit financial operations through MCP A2A AP2 Food Delivery & Payments — usually the final step of a payment, billing, or trading workflow. A call moves real money.
This tool commits financial obligations by reversing previous payment transactions. Even though it requires user authorization via AP2 cryptographic mandates, the ability to initiate refunds—which move money back to customers—makes this a Financial category tool.
From the tool's definition Tool name 'process_refund' and description 'Process refund via Stripe' directly indicates movement of money. Context shows this is part of a payments-enabled food delivery system with Stripe integration.
Attacks that exploit this kind of access
Process refund via Stripe. Requests user authorization, then sends mandate to Stripe. It is categorised as a Financial tool in the MCP A2A AP2 Food Delivery & Payments MCP Server, which means it involves financial transactions. Block by default and require explicit approval.
Register the MCP A2A AP2 Food Delivery & Payments MCP server in PolicyLayer and add a rule for process_refund: 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 A2A AP2 Food Delivery & Payments. Nothing to install.
process_refund 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 process_refund 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 process_refund. 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.
process_refund is provided by the MCP A2A AP2 Food Delivery & Payments MCP server (tas1337/mcp-a2a-ap2-im-hungry). 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 →