create_recipient

THE RISK

Medium Risk

Why create_recipient needs a policy

This tool creates and persists new beneficiary records in Argentina's tax authority system. While the action itself is reversible (recipients can be removed), it directly supports the downstream financial operation of split payments. The write operation affects regulatory compliance records tied to actual payments, making it more severe than a simple data creation.

From the tool's definition 'Register a final beneficiary' indicates creation of a new entity in the AFIP system. The description explicitly states recipients are 'attached to a payment,' establishing a direct link to financial operations.

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

POLICY

How to control create_recipient

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

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "create_recipient": {
      "limits": [
        {
          "counter": "create_recipient_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

create_recipient stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

Create a free account and register Mcp Afip — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

LIMIT THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Mcp Afip tools

Financial authorize_transaction Authorize a transaction (reserve funds without capturing) via Braintree GraphQL authorizeP Financial cancel_collection Cancel a scheduled collection request Financial cancel_credit Cancel an authorized-but-uncaptured credit payment. Financial cancel_payment Attempt to cancel a payment that has not yet settled. Iniciador endpoint: POST /payments/{ Financial cancel_payment_intent Cancel a payment intent that has not yet been captured. Fails on already-captured intents; Financial cancel_recurrence Cancel an active recurrence. Future charges will stop; already-charged cycles are untouche Financial cancel_subscription Cancel a subscription by ID Financial revoke_token Revoke an issued access_token or refresh_token at POST /v1/token/revoke. Use to terminate

All 1300 Mcp Afip tools →

Write tools on other servers

M-Team MCP Server download_torrent YouTube MCP Server generate_video_title Android Forensics ADB MCP Server combine_reports 0xarchive web3_signup

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Argument validation → Checking tool call arguments against schema and policy before they run.
Scoped token → Per-person credentials that grant a defined subset of servers and tools.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about create_recipient

What does the create_recipient tool do? +

Register a final beneficiary (required for regulatory split payments). Up to 10 recipients can later be attached to a payment. It is categorised as a Write tool in the Mcp Afip MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on create_recipient? +

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

create_recipient is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit create_recipient? +

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

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

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

CHECK YOUR STACK →