Modify an existing order on Hyperliquid exchange.
AI agents use modify_order to create or update resources in Hyperliquid — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Hyperliquid environment.
This tool modifies financial orders reversibly (orders can be cancelled or replaced with new orders). While it operates in a financial context, the modification itself is not a financial transaction that moves money directly—it adjusts order parameters. However, given the context of a decentralized exchange where order modifications affect trading positions and market exposure, this warrants high severity.
From the tool's definition Tool modifies an existing order on a financial exchange (Hyperliquid). Description states 'Modify an existing order' which is a reversible state change to a trading position.
Attacks that exploit this kind of access
Modify an existing order on Hyperliquid exchange. It is categorised as a Write tool in the Hyperliquid MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Hyperliquid 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 Hyperliquid. 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 Hyperliquid MCP server (midodimori/hyperliquid-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 →