Get account positions
AI agents call positions 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 retrieves account position data without any side effects, matching the Read category definition. While the underlying data relates to financial instruments, the tool itself only queries and returns information—it does not move money, execute trades, or modify any state. Severity is low as misuse would only expose sensitive account information without causing financial harm or irreversible damage.
From the tool's definition Tool name 'positions' and description 'Get account positions' indicate data retrieval with no modification or execution. This is a query operation that retrieves existing portfolio/account position information.
Attacks that exploit this kind of access
Get account positions. 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 positions: 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.
positions 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 positions 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 positions. 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.
positions 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 →