Get positions for a given nickname
AI agents call get_positions to retrieve information from QuantPlay 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 trading position data for analysis. While it is a Read operation (no side effects), it deserves medium severity because exposing position data to an untrusted agent could enable information leakage about financial holdings, timing of trades, or portfolio composition—useful for social engineering or market manipulation. The confidence is high due to clear Read semantics in the name and description.
From the tool's definition Tool name 'get_positions' and description 'Get positions for a given nickname' indicate a retrieval operation with no modification. Sibling tools include 'get_accounts' and 'get_holdings', which are clearly Read operations.
Attacks that exploit this kind of access
Get positions for a given nickname. It is categorised as a Read tool in the QuantPlay MCP Server MCP Server, which means it retrieves data without modifying state.
Register the QuantPlay MCP Server MCP server in PolicyLayer and add a rule for get_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 QuantPlay MCP Server. Nothing to install.
get_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 get_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 get_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.
get_positions is provided by the QuantPlay MCP Server MCP server (quantplay/quantplay-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 →