positions_get_by_ticket
Get an open position by its ticket.
This record as markdown: /tools/af7007-mcp-trader/positions-get-by-ticket.md
What positions_get_by_ticket does on MCP Trader Server
AI agents call positions_get_by_ticket to retrieve information from MCP Trader Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why positions_get_by_ticket is rated Low
This tool queries and retrieves existing position data based on a ticket identifier. It performs no modifications, deletions, or financial transactions. While it operates in a trading context, the tool itself only reads and returns information about an open position.
From the tool's definition Tool name 'positions_get_by_ticket' and description 'Get an open position by its ticket' indicate data retrieval with no side effects. The verb 'get' and the action of retrieving position information by identifier are read-only operations.
Attacks that exploit this kind of access
The rule that runs positions_get_by_ticket safely
PolicyLayer is an MCP gateway: it sits between your AI agents and MCP Trader Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For positions_get_by_ticket, this is the rule to start with:
positions_get_by_ticket is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect MCP Trader Server, apply this rule, and every positions_get_by_ticket call is checked against it from then on.
Questions about positions_get_by_ticket
Get an open position by its ticket. It is categorised as a Read tool in the MCP Trader Server MCP Server, which means it retrieves data without modifying state.
Register the MCP Trader Server MCP server in PolicyLayer and add a rule for positions_get_by_ticket: 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 MCP Trader Server. Nothing to install.
positions_get_by_ticket 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_get_by_ticket 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_get_by_ticket. 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_get_by_ticket is provided by the MCP Trader Server MCP server (af7007/mcp-trader). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on MCP Trader Server, and thousands of servers like it.
This server
Across the catalogue