AI agents call tiger_cancel_order to permanently remove resources in Tiger MCP — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Order cancellation qualifies as Destructive because it irreversibly modifies the state of a financial order (removing it from the market) and cannot be easily reversed. Although not as severe as a data deletion, the irreversibility and financial consequences (lost orders, missed opportunities, impact on portfolio state) place it above Write (which is reversible through correction) but below Financial (which directly…
From the tool's definition Tool name 'tiger_cancel_order' in the context of a broker API integration indicates it performs an order cancellation operation.
Documented attack patterns abuse exactly the kind of access tiger_cancel_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_cancel_order:
{
"version": "1",
"default": "deny",
"hide": [
"tiger_cancel_order"
]
} tiger_cancel_order disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.
Free to start. No card required.
tiger_cancel_order. It is categorised as a Destructive tool in the Tiger MCP MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Tiger MCP server in PolicyLayer and add a rule for tiger_cancel_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_cancel_order is a Destructive 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_cancel_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_cancel_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_cancel_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.