Get all positions for a wallet address across all markets.
AI agents call get_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 queries and retrieves position data for a given wallet address. It performs no state changes, does not execute code or commands, does not delete data, and does not involve financial transactions. It is a straightforward data query operation, fitting the 'Read' category. Severity is low because misuse would only expose existing data the requester may already have access to.
From the tool's definition Tool name 'get_positions' and description 'Get all positions for a wallet address across all markets' indicate a retrieval operation with no side effects.
Attacks that exploit this kind of access
Get all positions for a wallet address across all markets. 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_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_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 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 →