Detect possible carriers for a tracking number
AI agents call detect_carrier to retrieve information from Trackmage MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves or identifies carrier information for a tracking number without modifying data, triggering external operations, or affecting system state. It is a pure read operation with minimal blast radius if misused—at worst, it could reveal logistics metadata about tracked shipments, but cannot create, modify, delete, or execute operations.
From the tool's definition Tool name 'detect_carrier' and description 'Detect possible carriers for a tracking number' indicate a query operation that identifies carrier information based on existing tracking data.
Attacks that exploit this kind of access
Detect possible carriers for a tracking number. It is categorised as a Read tool in the Trackmage MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Trackmage MCP Server MCP server in PolicyLayer and add a rule for detect_carrier: 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 Trackmage MCP Server. Nothing to install.
detect_carrier 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 detect_carrier 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 detect_carrier. 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.
detect_carrier is provided by the Trackmage MCP Server MCP server (trackmage/trackmage-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →