Performs follow-up queries on cached shipment records from query_shipments using query_id.
AI agents call query_shipments_followup 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 retrieves and queries existing shipment data from cache without creating, modifying, deleting, or executing external operations. It is a standard Read operation that accesses data with no side effects or irreversible consequences.
From the tool's definition Tool description states it 'Performs follow-up queries on cached shipment records' using a query_id. The word 'queries' combined with 'cached records' indicates data retrieval without modification.
Attacks that exploit this kind of access
Performs follow-up queries on cached shipment records from query_shipments using query_id. 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 query_shipments_followup: 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.
query_shipments_followup 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 query_shipments_followup 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 query_shipments_followup. 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.
query_shipments_followup 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 →