Schedule a UPS package pickup at a specific address and time. Provide the pickup date, time window, address, and package details. Returns a confirmation number to reference or cancel the pickup.
AI agents use schedule_pickup to create or update resources in UPS MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your UPS MCP Server environment.
The tool creates a new service request (pickup scheduling) that is reversible via the sibling tool 'cancel_pickup'. This is a Write operation because it creates/modifies data and initiates a real-world logistics action, but it is not Destructive (can be undone by cancellation) nor Destructive (irreversible).
From the tool's definition Tool description states it will 'Schedule a UPS package pickup' and 'Returns a confirmation number' — this creates a new pickup request in the UPS system, modifying their operational state by adding a scheduled pickup.
Attacks that exploit this kind of access
Schedule a UPS package pickup at a specific address and time. Provide the pickup date, time window, address, and package details. Returns a confirmation number to reference or cancel the pickup. It is categorised as a Write tool in the UPS MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the UPS MCP Server MCP server in PolicyLayer and add a rule for schedule_pickup: 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 UPS MCP Server. Nothing to install.
schedule_pickup 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 schedule_pickup 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 schedule_pickup. 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.
schedule_pickup is provided by the UPS MCP Server MCP server (roscoej/ups-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 →