get_carrier_performance
AI agents call get_carrier_performance 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 appears to retrieve carrier performance data without modifying, deleting, or executing external operations. It fits the Read category as a data retrieval operation. However, empty description and lack of explicit detail reduces confidence to 0.75 rather than higher. No financial, destructive, or execution risks evident from available information.
From the tool's definition Tool name 'get_carrier_performance' combined with server context (shipment tracking) suggests querying performance metrics. Server description emphasizes tracking and retrieval of package information.
Attacks that exploit this kind of access
get_carrier_performance. 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_carrier_performance: 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_carrier_performance 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_carrier_performance 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_carrier_performance. 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_carrier_performance 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 →