Get all user positions in a specific market.
AI agents call get_market_positions to retrieve information from Question Market without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves information about user positions. It does not create, modify, delete, or execute any operations. There is no financial transaction, no code execution, and no destructive action. The blast radius of misuse is minimal—an attacker could view a user's market positions but could not alter them, drain funds, or cause irreversible harm.
From the tool's definition The tool description states 'Get all user positions in a specific market' — 'Get' is a read-only retrieval operation with no side effects. It queries and returns data about existing positions without modifying, deleting, or executing operations.
Attacks that exploit this kind of access
Get all user positions in a specific market. It is categorised as a Read tool in the Question Market MCP Server, which means it retrieves data without modifying state.
Register the Question Market MCP server in PolicyLayer and add a rule for get_market_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 Question Market. Nothing to install.
get_market_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_market_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_market_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_market_positions is provided by the Question Market MCP server (qmrkt/mcp-server). 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 →