predict.price-history

Time-series price (implied-probability) history for a Polymarket outcome token. Pass the CLOB token id and an interval (1h, 6h, 1d, 1w, 1m, max). Returns timestamped price points — for charting how a market

Server Mcp @2sio/mcp
Category Read
Risk class Low
Parameters 00 required

What predict.price-history does on Mcp

AI agents call predict.price-history to retrieve information from Mcp without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Why predict.price-history needs a policy

The tool retrieves time-series price history data from Polymarket for visualization/analysis purposes. It is a query operation that fetches existing data with no side effects, no code execution, no financial transactions, and no data modification or deletion. Despite the server's focus on financial settlement infrastructure, this specific tool only reads market data.

From the tool's definition Tool description states it 'Returns timestamped price points — for charting how a market', indicating retrieval of historical price data without modification, deletion, or execution of trades.

Questions about predict.price-history

What does the predict.price-history tool do? +

Time-series price (implied-probability) history for a Polymarket outcome token. Pass the CLOB token id and an interval (1h, 6h, 1d, 1w, 1m, max). Returns timestamped price points — for charting how a market. It is categorised as a Read tool in the Mcp MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on predict.price-history? +

Register the MCP server in PolicyLayer and add a rule for predict.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 Mcp. Nothing to install.

What risk level is predict.price-history? +

predict.price-history is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit predict.price-history? +

Yes. Add a rate_limit block to the predict.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.

How do I block predict.price-history completely? +

Set action: deny in the PolicyLayer policy for predict.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.

What MCP server provides predict.price-history? +

predict.price-history is provided by the MCP server (@2sio/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// LOOK UP ANOTHER 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 →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.