get_tracking
AI agents call get_tracking to retrieve information from eShipz Tracking MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool appears to retrieve tracking information for shipments from the eShipz API. This is a read-only operation that queries existing data. While the description is empty (reducing confidence slightly), the tool name and sibling tools on the same server all follow patterns consistent with read operations. No creation, modification, deletion, code execution, or financial operations are indicated.
From the tool's definition Tool name 'get_tracking' combined with server context (shipment tracking functionality) and sibling tools (get_carrier_performance, get_shipment_details_from_query, get_shipments, query_shipments) all indicate retrieval operations.
Attacks that exploit this kind of access
get_tracking. It is categorised as a Read tool in the eShipz Tracking MCP Server MCP Server, which means it retrieves data without modifying state.
Register the eShipz Tracking MCP Server MCP server in PolicyLayer and add a rule for get_tracking: 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 eShipz Tracking MCP Server. Nothing to install.
get_tracking 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 get_tracking 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 get_tracking. 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.
get_tracking is provided by the eShipz Tracking MCP Server MCP server (kavinvetrivel/eshipz-mcp). 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 →