AI agents use modify_order to create or update resources in Moomoo Api — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Moomoo Api environment.
Modify_order alters existing trading orders, which is a Write operation (creates or modifies data reversibly). It is not Destructive because order modifications are typically reversible via further modifications or cancellations. It could have financial consequences if the modification changes trade parameters, but the core action is modifying data rather than moving money directly. Confidence is slightly reduced (0.
From the tool's definition Tool named 'modify_order' on a trading platform (Moomoo) that manages trading accounts and executes trades. Sibling tools include 'cancel_order' and 'get_deals', indicating this server handles order management operations.
Documented attack patterns abuse exactly the kind of access modify_order gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Moomoo Api, and nothing reaches the server without passing your rules. This is the rule we recommend for modify_order:
{
"version": "1",
"default": "deny",
"tools": {
"modify_order": {
"limits": [
{
"counter": "modify_order_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}modify_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.
Free to start. No card required.
modify_order. It is categorised as a Write tool in the Moomoo Api MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Moomoo Api MCP server in PolicyLayer and add a rule for modify_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 Moomoo Api. Nothing to install.
modify_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 modify_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 modify_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.
modify_order is provided by the Moomoo Api MCP server (litash/moomoo-api-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Moomoo Api, 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.
22 Moomoo Api tools catalogued and risk-classified — across an index of 43,000+ MCP servers.