Get list of brokerage accounts
AI agents call getAccounts to retrieve information from TradeStation MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and returns account information without creating, modifying, deleting, or executing any operations. It is purely informational. While account details are sensitive financial information, the tool itself performs only a read operation. Severity is low because retrieving account list metadata does not directly expose account balances, enable transactions, or cause irreversible changes.
From the tool's definition Tool name is 'getAccounts' and description states 'Get list of brokerage accounts' — a retrieval operation with no data modification or side effects.
Attacks that exploit this kind of access
Get list of brokerage accounts. It is categorised as a Read tool in the TradeStation MCP Server MCP Server, which means it retrieves data without modifying state.
Register the TradeStation MCP Server MCP server in PolicyLayer and add a rule for getAccounts: 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 TradeStation MCP Server. Nothing to install.
getAccounts 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 getAccounts 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 getAccounts. 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.
getAccounts is provided by the TradeStation MCP Server MCP server (maven81g/tradestation_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 →