get_shipment_details_from_query

Returns one shipment detail record from a cached query context using AWB or order ID.

Server eShipz Tracking MCP Server kavinvetrivel/eshipz-mcp
Category Read
Risk class Low
Parameters 00 required

What get_shipment_details_from_query does on eShipz Tracking MCP Server

AI agents call get_shipment_details_from_query 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.

Why get_shipment_details_from_query needs a policy

This tool retrieves and queries existing shipment data without side effects. It does not create, modify, delete, or execute operations; it simply fetches cached results by AWB or order ID. The blast radius of misuse is minimal — at worst, an attacker could view shipment details they shouldn't, but no data is altered, destroyed, or financial transactions are triggered.

From the tool's definition Tool description states it 'Returns one shipment detail record from a cached query context' — a retrieval operation with no modification, deletion, or execution of external systems.

Questions about get_shipment_details_from_query

What does the get_shipment_details_from_query tool do? +

Returns one shipment detail record from a cached query context using AWB or order ID. It is categorised as a Read tool in the eShipz Tracking MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_shipment_details_from_query? +

Register the eShipz Tracking MCP Server MCP server in PolicyLayer and add a rule for get_shipment_details_from_query: 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.

What risk level is get_shipment_details_from_query? +

get_shipment_details_from_query is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_shipment_details_from_query? +

Yes. Add a rate_limit block to the get_shipment_details_from_query 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.

How do I block get_shipment_details_from_query completely? +

Set action: deny in the PolicyLayer policy for get_shipment_details_from_query. 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.

What MCP server provides get_shipment_details_from_query? +

get_shipment_details_from_query 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.

// LOOK UP ANOTHER 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 →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.