create_shipment
AI agents use create_shipment to create or update resources in eShipz Tracking MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your eShipz Tracking MCP Server environment.
Creating a shipment constitutes a write operation that modifies system state by adding new shipment data. While not destructive (reversible via update/delete) and not directly financial (though shipments have business value), this is a write operation with medium-to-high blast radius if an AI agent creates unintended, duplicate, or fraudulent shipments at scale.
From the tool's definition Tool name 'create_shipment' indicates data creation. Sibling tools include 'fetch_and_create_shipment' and 'allocate_docket' which suggest the server manages shipment lifecycle operations.
Attacks that exploit this kind of access
create_shipment. It is categorised as a Write tool in the eShipz Tracking MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the eShipz Tracking MCP Server MCP server in PolicyLayer and add a rule for create_shipment: 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.
create_shipment is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the create_shipment 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 create_shipment. 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.
create_shipment 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 →