Update the shipment status of an order (Orders API v0). Used to mark MFN orders as ReadyForPickup, PickedUp, or RefusedPickup.
AI agents use update_shipment_status to create or update resources in Mcp Ap2 — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Mcp Ap2 environment.
This tool creates or modifies data reversibly by changing order shipment status. It does not delete data (not Destructive), does not execute arbitrary code (not Execute), and does not directly move money (not Financial). The blast radius is medium because incorrect shipment status updates could disrupt logistics operations and customer experience, but the changes are not permanent and can be corrected.
From the tool's definition Tool name is 'update_shipment_status' and description states 'Update the shipment status' — indicating modification of existing order data.
Documented attack patterns abuse exactly the kind of access update_shipment_status gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Mcp Ap2, and nothing reaches the server without passing your rules. This is the rule we recommend for update_shipment_status:
{
"version": "1",
"default": "deny",
"tools": {
"update_shipment_status": {
"limits": [
{
"counter": "update_shipment_status_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}update_shipment_status stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Update the shipment status of an order (Orders API v0). Used to mark MFN orders as ReadyForPickup, PickedUp, or RefusedPickup. It is categorised as a Write tool in the Mcp Ap2 MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Mcp Ap2 MCP server in PolicyLayer and add a rule for update_shipment_status: 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 Mcp Ap2. Nothing to install.
update_shipment_status 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 update_shipment_status 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 update_shipment_status. 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.
update_shipment_status is provided by the Mcp Ap2 MCP server (@codespar/mcp-ap2). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Mcp Ap2, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
1300 Mcp Ap2 tools catalogued and risk-classified — across an index of 43,000+ MCP servers.