Medium Risk

generate_label

Generate shipping label for an order

How to control generate_label ↓

What generate_label does on Mcp Afip

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

Generating a shipping label creates a new, reversible record in the system (a label can be voided or regenerated). It modifies order state by producing documentation, but does not delete data, execute arbitrary code, or move money. This is a Write operation.

From the tool's definition The tool name is 'generate_label' and the description states it 'Generate[s] shipping label for an order'. This creates a new shipping label document.

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

How to control generate_label

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

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

generate_label 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 generate_label

What does the generate_label tool do? +

Generate shipping label for an order. 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 generate_label? +

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

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

Can I rate-limit generate_label? +

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

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

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