Critical Risk →

create_push_payment

Send a push payment notification to a Nequi user

How to control create_push_payment ↓

What create_push_payment does on Mcp Afip

AI agents use create_push_payment 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 create_push_payment needs a policy

The tool name 'create_push_payment' and description explicitly indicate it sends a payment notification via Nequi (a payment platform), which constitutes a financial transaction. Push payments involve moving money or committing financial obligations. Misuse could result in unauthorized payments being triggered, making this critical severity.

From the tool's definition 'Send a push payment notification to a Nequi user' — initiates or triggers a financial payment transaction

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

How to control create_push_payment

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 create_push_payment:

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

Any call to create_push_payment 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 create_push_payment

What does the create_push_payment tool do? +

Send a push payment notification to a Nequi user. 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 create_push_payment? +

Register the Mcp Afip MCP server in PolicyLayer and add a rule for create_push_payment: 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 create_push_payment? +

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

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

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

create_push_payment 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.