Get shipment history with analytics — 90-day view of all shipments, delivery rates, carrier performance. Requires API key.
AI agents call list_shipments to retrieve information from CerebroChain MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
list_shipments retrieves and queries shipment data for analytics purposes without creating, modifying, deleting, or executing any operations. This is a standard read operation with limited blast radius—exposure would allow viewing logistics data but not altering operations, executing commands, or affecting finances. The requirement for an API key mitigates exposure but does not change the category.
From the tool's definition Tool description states 'Get shipment history with analytics — 90-day view of all shipments, delivery rates, carrier performance.' The verb 'Get' and focus on historical data retrieval with no modification or execution capability indicate a read-only…
Attacks that exploit this kind of access
Get shipment history with analytics — 90-day view of all shipments, delivery rates, carrier performance. Requires API key. It is categorised as a Read tool in the CerebroChain MCP Server MCP Server, which means it retrieves data without modifying state.
Register the CerebroChain MCP Server MCP server in PolicyLayer and add a rule for list_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 CerebroChain MCP Server. Nothing to install.
list_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 list_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 list_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.
list_shipments is provided by the CerebroChain MCP Server MCP server (cerebrochain/cerebrochain-mcp-server). 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 →