AI agents use create_order to commit financial operations through Crypto Multi-MCP Hub — usually the final step of a payment, billing, or trading workflow. A call moves real money.
Creating a trading order on a crypto platform directly commits financial resources. Given the server context of autonomous trading execution with on-chain operations, this tool can initiate irreversible financial transactions. The description is minimal but the server context and sibling tools (execute_approved_order, execute_dex_swap, cancel_order) confirm this is a financial order creation tool.
From the tool's definition 'Creates an order' on a server described as supporting 'autonomous trading agent execution' and 'on-chain data'
Documented attack patterns abuse exactly the kind of access create_order gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Crypto Multi-MCP Hub, and nothing reaches the server without passing your rules. This is the rule we recommend for create_order:
{
"version": "1",
"default": "deny",
"tools": {
"create_order": {
"deny_if": [
{
"conditions": [],
"on_deny": "Requires human approval."
}
]
}
}
} Any call to create_order is blocked until a human approves it. The rest of the server keeps working.
Free to start. No card required.
Creates an order. It is categorised as a Financial tool in the Crypto Multi-MCP Hub MCP Server, which means it involves financial transactions. Block by default and require explicit approval.
Register the Crypto Multi-MCP Hub 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 Crypto Multi-MCP Hub. 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 Crypto Multi-MCP Hub MCP server (pellenybe/crypto-mcp-server---by-corax-colab). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Crypto Multi-MCP Hub, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
48 Crypto Multi-MCP Hub tools catalogued and risk-classified — across an index of 43,000+ MCP servers.