Add a new delivery to Parcel for tracking
AI agents use add_delivery to create or update resources in Parcel MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Parcel MCP Server environment.
This tool creates new data (shipment records) in the parcel tracking system, which is reversible—deliveries can be removed or updated. It has moderate blast radius if misused (e.g., creating spurious shipments, polluting the tracking database), but does not delete data, execute arbitrary code, or involve financial transactions. Classified as Write rather than Read (retrieves data) or Execute (runs code/commands).
From the tool's definition Tool name 'add_delivery' and description 'Add a new delivery to Parcel for tracking' indicate creation of new shipment records in the delivery tracking system.
Attacks that exploit this kind of access
Add a new delivery to Parcel for tracking. It is categorised as a Write tool in the Parcel MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Parcel MCP Server MCP server in PolicyLayer and add a rule for add_delivery: 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 Parcel MCP Server. Nothing to install.
add_delivery 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 add_delivery 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 add_delivery. 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.
add_delivery is provided by the Parcel MCP Server MCP server (nova-3951/parcel-api-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 →