CLOB price history for one outcome.
AI agents call get_market_price_history to retrieve information from Polymarket Research without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves historical price data from a CLOB (central limit order book) for a single outcome on Polymarket. It performs a query operation with no side effects, no state modification, no code execution, and no financial transactions. It aligns with the 'Read' category of data retrieval operations.
From the tool's definition Tool name 'get_market_price_history' retrieves historical pricing data. Description 'CLOB price history for one outcome' indicates querying past data. Server is explicitly 'Read-only MCP server' with 'public APIs' as backing.
Attacks that exploit this kind of access
CLOB price history for one outcome. It is categorised as a Read tool in the Polymarket Research MCP Server, which means it retrieves data without modifying state.
Register the Polymarket Research MCP server in PolicyLayer and add a rule for get_market_price_history: 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 Research. Nothing to install.
get_market_price_history 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_price_history 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_price_history. 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_price_history is provided by the Polymarket Research MCP server (yoppav/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 →