create_order
Create an order for an eSIM package. Returns a Stripe checkout URL where the user can pay. Requires a session key (from a previous tool call's structuredContent) or creates one automatically.
This record as markdown: /tools/com-gitsim-chat/create-order.md
What create_order does on Gitsim Chat
AI agents use create_order to commit financial operations through Gitsim Chat, usually the final step of a payment, billing, or trading workflow. A call moves real money.
| Parameter | Type | Required | Description |
|---|---|---|---|
package_id | string | Yes | The package ID to order |
session_key | string | — | Session key from a previous tool call. If not provided, a new session is created automatically. |
referral_code | string | — | Optional referral code for a discount |
Parameters from the server's own tool schema.
Why create_order is rated Critical
This tool initiates a financial transaction by creating an order and directing the user to a Stripe payment page. It directly commits the user to a purchase/financial obligation, making it Financial category with critical severity since misuse could result in unauthorized charges.
From the tool's definition Create an order for an eSIM package. Returns a Stripe checkout URL where the user can pay.
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 Gitsim Chat, 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:
Any call to create_order is blocked until a human approves it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Gitsim Chat, apply this rule, and every create_order call is checked against it from then on.
Questions about create_order
Create an order for an eSIM package. Returns a Stripe checkout URL where the user can pay. Requires a session key (from a previous tool call's structuredContent) or creates one automatically. It is categorised as a Financial tool in the Gitsim Chat MCP Server, which means it involves financial transactions. Block by default and require explicit approval.
create_order accepts 3 parameters: package_id, session_key, referral_code. Required: package_id. The full parameter table on this page comes from the server's own tool schema.
Register the Gitsim Chat 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 Gitsim Chat. Nothing to install.
create_order is a Financial tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
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 Gitsim Chat MCP server (https://chat.gitsim.com/api/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Gitsim Chat, and thousands of servers like it.
Across the catalogue