schedule_pickup
Schedule material pickup with a transport partner. Buyer coordinates logistics directly.
This record as markdown: /tools/nitrostack/schedule-pickup.md
What schedule_pickup does on Nitrostack
AI agents use schedule_pickup to create or update resources in Nitrostack, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Nitrostack environment.
Why schedule_pickup is rated Medium
Creates a pickup order that modifies logistics state; reversible but affects supply chain operations.
From the tool's definition Schedule material pickup with a transport partner. Coordinates logistics directly.
Attacks that exploit this kind of access
The rule that runs schedule_pickup safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Nitrostack, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For schedule_pickup, this is the rule to start with:
schedule_pickup 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Nitrostack, apply this rule, and every schedule_pickup call is checked against it from then on.
Questions about schedule_pickup
Schedule material pickup with a transport partner. Buyer coordinates logistics directly. It is categorised as a Write tool in the Nitrostack MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Nitrostack 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 Nitrostack. 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 Nitrostack MCP server (nitrocloudofficial/nitrostack). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Nitrostack, and thousands of servers like it.
This server
Across the catalogue