get_positions
AI agents call get_positions to retrieve information from Polymarket without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Despite the empty description, the tool name, server classification as read-only, and context from sibling tools all consistently indicate this retrieves position information without side effects. No financial transactions, writes, or destructive operations are possible on a read-only CLOB data interface. Low severity due to informational-only impact.
From the tool's definition Server explicitly described as 'read-only interface' with tools for 'querying markets, wallets, and order books.' Tool name 'get_positions' follows the established pattern of read-only getter methods (get_activity, get_book, get_market_by_slug, get_price, etc.
Attacks that exploit this kind of access
get_positions. It is categorised as a Read tool in the Polymarket MCP Server, which means it retrieves data without modifying state.
Register the Polymarket 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 Polymarket. 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 Polymarket MCP server (pr1m8/polymarket-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 →