tiger_remove_account

THE RISK

Critical Risk

Why tiger_remove_account needs a policy

This tool performs an irreversible action (account deletion) that cannot be undone and would eliminate critical financial and trading infrastructure. This makes it Destructive rather than merely Write. The critical severity reflects the high-impact nature of account removal in a financial trading context, where loss of account access affects all associated positions, data, and capabilities.

From the tool's definition Tool name is 'tiger_remove_account' with no description provided. In context of a trading/brokerage MCP server, 'remove_account' indicates deletion or removal of an account. The sibling tool 'tiger_add_account' suggests account lifecycle management.

Documented attack patterns abuse exactly the kind of access tiger_remove_account gives an agent:

POLICY

How to control tiger_remove_account

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_remove_account:

policy.json

{
  "version": "1",
  "default": "deny",
  "hide": [
    "tiger_remove_account"
  ]
}

tiger_remove_account disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.

Create a free account and register Tiger MCP — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

RESTRICT THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Tiger MCP tools

Financial tiger_place_order tiger_place_order Financial tiger_modify_order tiger_modify_order Destructive tiger_cancel_order tiger_cancel_order Write tiger_add_account tiger_add_account Write tiger_set_default_data_account tiger_set_default_data_account Write tiger_set_default_trading_account tiger_set_default_trading_account Read tiger_get_account_info tiger_get_account_info Read tiger_get_account_status tiger_get_account_status

All 23 Tiger MCP tools →

Destructive tools on other servers

Android Forensics ADB MCP Server create_full_backup 0xarchive web3_revoke_key Frida Game Hacking MCP clear_scan cPanel MCP Server clear_spam_box

Go deeper

Critical-risk tools in Tiger MCP → Every critical-risk tool this server exposes, in one view.
All critical-risk MCP tools → Every critical-risk tool across the catalogue, and the policy pattern that contains them.
The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Blast radius → How much damage one compromised or confused agent can do — and how to bound it.
Tool call approval → Approval gates on individual tool calls: auto-allow, prompt, or deny.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about tiger_remove_account

What does the tiger_remove_account tool do? +

tiger_remove_account. 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.

How do I enforce a policy on tiger_remove_account? +

Register the Tiger MCP server in PolicyLayer and add a rule for tiger_remove_account: 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.

What risk level is tiger_remove_account? +

tiger_remove_account is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit tiger_remove_account? +

Yes. Add a rate_limit block to the tiger_remove_account 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.

How do I block tiger_remove_account completely? +

Set action: deny in the PolicyLayer policy for tiger_remove_account. 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.

What MCP server provides tiger_remove_account? +

tiger_remove_account 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.

Enforce policy on every Tiger MCP tool call.

Start from Tiger MCP, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →