Medium Risk

create_pickup

Create a pickup/collection request (retiro)

How to control create_pickup ↓

What create_pickup does on Mcp Afip

AI agents use create_pickup to create or update resources in Mcp Afip — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Mcp Afip environment.

Medium Risk

Why create_pickup needs a policy

This tool creates a new resource (a pickup request) in the Argentine tax authority's invoicing system. It modifies system state by adding a new request record, but the action is reversible (the request can be cancelled or modified). This is a Write operation rather than Execute because it does not run arbitrary code or trigger external operations with argument-dependent effects.

From the tool's definition Tool name 'create_pickup' and description 'Create a pickup/collection request (retiro)' indicate a CREATE operation that establishes a new pickup/collection request in the AFIP system.

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

How to control create_pickup

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

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "create_pickup": {
      "limits": [
        {
          "counter": "create_pickup_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

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

  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.
LIMIT THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about create_pickup

What does the create_pickup tool do? +

Create a pickup/collection request (retiro). 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_pickup? +

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

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

Can I rate-limit create_pickup? +

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

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

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