Track a shipment by tracking number
AI agents call track_shipment 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 tracking information, which is a read-only retrieval operation with no side effects. It returns status data about an existing shipment based on a tracking identifier. The blast radius of misuse is minimal—an attacker could gain visibility into shipment details but cannot modify, delete, or execute any operations.
From the tool's definition Track a shipment by tracking number — retrieves shipment status information without modifying any data.
Documented attack patterns abuse exactly the kind of access track_shipment 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_shipment:
{
"version": "1",
"default": "deny",
"tools": {
"track_shipment": {}
}
} track_shipment 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 a shipment by tracking number. 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_shipment: 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_shipment 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_shipment 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_shipment. 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_shipment 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.