Cria um refund via POST /api/v1/refund (por transactionEndToEndId).
AI agents use woovi_create_refund to commit financial operations through Payments MCP — usually the final step of a payment, billing, or trading workflow. A call moves real money.
Refunds move money back to customers and represent financial obligations being reversed. Unauthorized or erroneous refund creation could result in immediate monetary loss, customer disputes, reconciliation failures, and regulatory exposure. This is a direct financial transaction with maximum blast radius if misused by a compromised agent.
From the tool's definition Tool creates refunds via payment API (POST /api/v1/refund). Server context shows integration with payment gateways Pagar.me and Woovi/OpenPix. Tool description states 'Cria um refund' (creates a refund) by transaction ID.
Attacks that exploit this kind of access
Cria um refund via POST /api/v1/refund (por transactionEndToEndId). It is categorised as a Financial tool in the Payments MCP MCP Server, which means it involves financial transactions. Block by default and require explicit approval.
Register the Payments MCP server in PolicyLayer and add a rule for woovi_create_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 Payments MCP. Nothing to install.
woovi_create_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 woovi_create_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 woovi_create_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.
woovi_create_refund is provided by the Payments MCP server (lpillonwp/mcp-payments). 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 →