Track multiple Correios packages in a single call (up to 50 codes)
AI agents call track_bulk to retrieve information from Mcp Afip without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries shipment status from Correios (Brazilian postal service). It returns data without side effects. Although it relates to an AFIP server (Argentine tax authority), the tool itself performs only read operations on package tracking data. The 'up to 50 codes' parameter limits scope but does not change the non-destructive nature of the operation.
From the tool's definition 'Track multiple Correios packages in a single call' — purely retrieves tracking information about shipments with no modification, deletion, or execution of code.
Documented attack patterns abuse exactly the kind of access track_bulk gives an agent:
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 track_bulk:
{
"version": "1",
"default": "deny",
"tools": {
"track_bulk": {}
}
} track_bulk is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Track multiple Correios packages in a single call (up to 50 codes). It is categorised as a Read tool in the Mcp Afip MCP Server, which means it retrieves data without modifying state.
Register the Mcp Afip MCP server in PolicyLayer and add a rule for track_bulk: 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.
track_bulk is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the track_bulk 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.
Set action: deny in the PolicyLayer policy for track_bulk. 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.
track_bulk 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.
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.