create_order
A financial tool on the PineLabs Plural PG — Payment Gateway MCP server.
This record as markdown: /tools/io-github-plural-pinelabs-pinelabs-online-mcp/create-order.md
What create_order does on PineLabs Plural PG — Payment Gateway MCP Server
AI agents use create_order to commit financial operations through PineLabs Plural PG — Payment Gateway MCP Server, usually the final step of a payment, billing, or trading workflow. A call moves real money.
Why create_order is rated Critical
Although the description is empty, the server context is explicitly a payment gateway and sibling tools confirm financial transaction capabilities. 'create_order' on a PG server initiates a payment order, which commits a financial obligation. This falls squarely in the Financial category with critical severity due to potential for unauthorized financial commitments.
From the tool's definition Tool name 'create_order' on a Payment Gateway MCP Server described as handling payment orders, checkout, subscriptions & UPI via PineLabs Plural PG gateway; sibling tools include create_payment_link, create_payout, create_debit confirming financial operations…
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 PineLabs Plural PG — Payment Gateway MCP Server, 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 PineLabs Plural PG — Payment Gateway MCP Server, apply this rule, and every create_order call is checked against it from then on.
Questions about create_order
create_order is a financial tool on the PineLabs Plural PG — Payment Gateway MCP Server MCP server. It is categorised as a Financial tool in the PineLabs Plural PG — Payment Gateway MCP Server MCP Server, which means it involves financial transactions. Block by default and require explicit approval.
Register the PineLabs Plural PG — Payment Gateway MCP Server 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 PineLabs Plural PG — Payment Gateway MCP Server. 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 PineLabs Plural PG — Payment Gateway MCP Server MCP server (pypi:pinelabs-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on PineLabs Plural PG — Payment Gateway MCP Server, and thousands of servers like it.
This server
Across the catalogue