AI agents use aevo_create_order to commit financial operations through Aevo-MCP — usually the final step of a payment, billing, or trading workflow. A call moves real money.
Creating an order on a financial trading platform directly commits a financial obligation or initiates a trade. Even though the description is empty, the tool name combined with the server context (Aevo trading platform) and sibling tools strongly indicates this places real trading orders. Misuse could result in unintended financial exposure, making this Financial/critical.
From the tool's definition Tool name 'aevo_create_order' on a trading platform server described as enabling agents to 'execute trades easily'; sibling tools include aevo_build_order, aevo_cancel_order, confirming this is a trade order submission tool.
Attacks that exploit this kind of access
aevo_create_order. It is categorised as a Financial tool in the Aevo-MCP MCP Server, which means it involves financial transactions. Block by default and require explicit approval.
Register the Aevo- MCP server in PolicyLayer and add a rule for aevo_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 Aevo-MCP. Nothing to install.
aevo_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 aevo_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 aevo_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.
aevo_create_order is provided by the Aevo- MCP server (ribbon-finance/aevo-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →