Critical Risk →

pay_order

Pay an existing order (attach a charge/payment to an order in CREATED state)

How to control pay_order ↓

What pay_order does on Mcp Afip

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

Critical Risk

Why pay_order needs a policy

This tool directly moves money or commits financial obligations by attaching payment/charges to orders in an Argentine tax authority (AFIP) invoicing system. Misuse could result in unauthorized payments, fraud, or financial loss. Financial operations are the highest severity category.

From the tool's definition Tool description states 'Pay an existing order (attach a charge/payment to an order)' — the term 'charge/payment' explicitly indicates financial transaction processing.

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

How to control pay_order

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

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

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

  1. Create a free account and register Mcp Afip — 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 pay_order

What does the pay_order tool do? +

Pay an existing order (attach a charge/payment to an order in CREATED state). It is categorised as a Financial tool in the Mcp Afip MCP Server, which means it involves financial transactions. Block by default and require explicit approval.

How do I enforce a policy on pay_order? +

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

What risk level is pay_order? +

pay_order 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 pay_order? +

Yes. Add a rate_limit block to the pay_order 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 pay_order completely? +

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

pay_order is provided by the Mcp Afip MCP server (codespar/mcp-dev-latam). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Mcp Afip tool call.

Start from Mcp Afip, 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 Afip 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.