tiger_list_accounts
AI agents call tiger_list_accounts to retrieve information from Tiger MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The 'list' action is characteristic of Read operations that retrieve or query data without side effects. Although the description is empty (lowering confidence slightly), the tool name and server context strongly indicate this fetches account information for display/monitoring rather than modifying, executing trades, or moving money.
From the tool's definition Tool name 'tiger_list_accounts' with 'list' verb suggests data retrieval. Server context involves Tiger Brokers API integration for trading and portfolio management, making account listing a read operation to retrieve account information.
Documented attack patterns abuse exactly the kind of access tiger_list_accounts 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_list_accounts:
{
"version": "1",
"default": "deny",
"tools": {
"tiger_list_accounts": {}
}
}tiger_list_accounts is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
tiger_list_accounts. It is categorised as a Read tool in the Tiger MCP MCP Server, which means it retrieves data without modifying state.
Register the Tiger MCP server in PolicyLayer and add a rule for tiger_list_accounts: 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_list_accounts is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the tiger_list_accounts 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_list_accounts. 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_list_accounts 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.