create_order
Create a flight order with hold (no payment required). IMPORTANT: Before calling this tool, you MUST collect passenger information from the user. Ask for: full name (first and last), title (Mr/Ms/Mrs/Miss/Dr), gender (M/F), date of birth (YYYY-MM-DD), email, and phone number with country code. Th...
This record as markdown: /tools/nitrostack/create-order.md
What create_order does on Nitrostack
AI agents use create_order 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 create_order is rated Medium
This tool creates a new flight order, which is a reversible write operation—data is created and can presumably be modified or cancelled before payment. While it involves financial transactions, the tool itself does not move money or commit payment; it only creates a hold that requires later payment processing.
From the tool's definition Tool description states 'Create a flight order' and 'order will be held for later payment', indicating it creates and modifies booking data reversibly without immediate financial commitment.
Attacks that exploit this kind of access
The rule that runs create_order 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 create_order, this is the rule to start with:
create_order 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 create_order call is checked against it from then on.
Questions about create_order
Create a flight order with hold (no payment required). IMPORTANT: Before calling this tool, you MUST collect passenger information from the user. Ask for: full name (first and last), title (Mr/Ms/Mrs/Miss/Dr), gender (M/F), date of birth (YYYY-MM-DD), email, and phone number with country code. The order will be held for later payment. 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 create_order: 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.
create_order 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_order 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_order. 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_order 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