Critical Risk →

reverse_transaction

Reverse any Nequi transaction by transaction ID (refund flow)

How to control reverse_transaction ↓

What reverse_transaction does on Mcp Ap2

AI agents use reverse_transaction to commit financial operations through Mcp Ap2 — usually the final step of a payment, billing, or trading workflow. A call moves real money.

Critical Risk

Why reverse_transaction needs a policy

Reversing a transaction is a financial operation that moves funds back to the originator. This falls squarely in the Financial category as it commits financial obligations (refunds). The blast radius is critical because an AI agent could misuse this to reverse arbitrary transactions by ID, causing large-scale unintended fund movements.

From the tool's definition 'Reverse any Nequi transaction by transaction ID (refund flow)' — explicitly reverses financial transactions, initiating refund flows that move money

Documented attack patterns abuse exactly the kind of access reverse_transaction gives an agent:

How to control reverse_transaction

PolicyLayer is an MCP gateway — it sits between your AI agents and Mcp Ap2, and nothing reaches the server without passing your rules. This is the rule we recommend for reverse_transaction:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "reverse_transaction": {
      "deny_if": [
        {
          "conditions": [],
          "on_deny": "Requires human approval."
        }
      ]
    }
  }
}

Any call to reverse_transaction is blocked until a human approves it. The rest of the server keeps working.

  1. Create a free account and register Mcp Ap2 — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
GATE THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about reverse_transaction

What does the reverse_transaction tool do? +

Reverse any Nequi transaction by transaction ID (refund flow). It is categorised as a Financial tool in the Mcp Ap2 MCP Server, which means it involves financial transactions. Block by default and require explicit approval.

How do I enforce a policy on reverse_transaction? +

Register the Mcp Ap2 MCP server in PolicyLayer and add a rule for reverse_transaction: 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 Ap2. Nothing to install.

What risk level is reverse_transaction? +

reverse_transaction is a Financial tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit reverse_transaction? +

Yes. Add a rate_limit block to the reverse_transaction 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.

How do I block reverse_transaction completely? +

Set action: deny in the PolicyLayer policy for reverse_transaction. 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.

What MCP server provides reverse_transaction? +

reverse_transaction is provided by the Mcp Ap2 MCP server (@codespar/mcp-ap2). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Mcp Ap2 tool call.

Start from Mcp Ap2, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

Free to start. No card required.

1300 Mcp Ap2 tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.