Get user positions by wallet address. Returns all positions held by the user. No authentication required.
AI agents call polymarket_get_user_positions to retrieve information from Polymarket MCP Server 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 existing user position data from the prediction market without any side effects. It performs a straightforward data lookup based on a wallet address parameter.
From the tool's definition Tool description states 'Get user positions by wallet address. Returns all positions held by the user.' This is a retrieval operation with 'No authentication required' and no modification, deletion, or execution capability.
Attacks that exploit this kind of access
Get user positions by wallet address. Returns all positions held by the user. No authentication required. It is categorised as a Read tool in the Polymarket MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Polymarket MCP Server MCP server in PolicyLayer and add a rule for polymarket_get_user_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 MCP Server. Nothing to install.
polymarket_get_user_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 polymarket_get_user_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 polymarket_get_user_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.
polymarket_get_user_positions is provided by the Polymarket MCP Server MCP server (Curious-Layer/cl-mcp-polymarket). 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 →