tiger_modify_order
AI agents use tiger_modify_order to commit financial operations through Tiger MCP — usually the final step of a payment, billing, or trading workflow. A call moves real money.
On a brokerage/trading platform, modifying an order directly affects financial transactions — changing price, quantity, or order type can commit or alter financial obligations. Even with an empty description, the tool name and server context strongly indicate this is a financial operation. Severity is critical because misuse could result in unintended trades or significant financial loss.
From the tool's definition Tool name 'tiger_modify_order' on a trading server (Tiger Brokers API) that explicitly provides 'order execution' capabilities; sibling tools include 'tiger_cancel_order' confirming order management context.
Documented attack patterns abuse exactly the kind of access tiger_modify_order gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Tiger MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for tiger_modify_order:
{
"version": "1",
"default": "deny",
"tools": {
"tiger_modify_order": {
"deny_if": [
{
"conditions": [],
"on_deny": "Requires human approval."
}
]
}
}
} Any call to tiger_modify_order is blocked until a human approves it. The rest of the server keeps working.
Free to start. No card required.
tiger_modify_order. It is categorised as a Financial tool in the Tiger MCP MCP Server, which means it involves financial transactions. Block by default and require explicit approval.
Register the Tiger MCP server in PolicyLayer and add a rule for tiger_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 Tiger MCP. Nothing to install.
tiger_modify_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 tiger_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 tiger_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.
tiger_modify_order is provided by the Tiger MCP server (luxiaolei/tiger-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Tiger MCP, 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.
23 Tiger MCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.