Finds shipments that have been stuck in transit without tracking updates.
AI agents call get_shipments 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.
This tool queries existing shipment data to identify those stuck in transit. It performs a search/filter operation (Read category) with no data creation, modification, deletion, or external execution. The blast radius is low: worst case, an agent retrieves information about shipments, which poses minimal risk.
From the tool's definition Tool description states it 'Finds shipments' — a query/search operation that retrieves data about stuck shipments without modifying or deleting them. The verb 'Finds' indicates data retrieval with no side effects.
Attacks that exploit this kind of access
Finds shipments that have been stuck in transit without tracking updates. 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_shipments: 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_shipments 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_shipments 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_shipments. 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_shipments 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 →