Refund a paid order — full when
AI agents use wafle_checkout_order_refund to commit financial operations through wafle MCP server — usually the final step of a payment, billing, or trading workflow. A call moves real money.
Refunding a paid order is a financial operation that moves funds back to the customer. This represents a direct financial obligation and commitment. The incomplete description ('— full when') suggests capability to refund orders, which is inherently a Financial operation. Misuse by an AI agent could result in unauthorized refunds and monetary loss.
From the tool's definition Tool name contains 'refund' and description states 'Refund a paid order' — this directly moves money by reversing a payment transaction.
Attacks that exploit this kind of access
Refund a paid order — full when. It is categorised as a Financial tool in the wafle MCP server MCP Server, which means it involves financial transactions. Block by default and require explicit approval.
Register the wafle MCP server MCP server in PolicyLayer and add a rule for wafle_checkout_order_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 wafle MCP server. Nothing to install.
wafle_checkout_order_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 wafle_checkout_order_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 wafle_checkout_order_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.
wafle_checkout_order_refund is provided by the wafle MCP server MCP server (the33warehouse-tech/wafle-mcp). 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 →