polymarket.market.history

Get price history for a prediction market

SERVERApibase SOURCEapibase-mcp-client

Low RISK CLASS

Category Read

Parameters 31 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-whiteknightonhorse-apibase/polymarket.market.history.md

WHAT IT DOES

What polymarket.market.history does on Apibase

AI agents call polymarket.market.history to retrieve information from Apibase without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Parameter	Type	Required	Description
`days`	integer	—	Number of days of history (1-365)
`interval`	string	—	Price data interval for history (1h, 4h, 1d, or 1w)
`market_id`	string	Yes	Polymarket condition ID

Parameters from the server's own tool schema.

RISK

Why polymarket.market.history is rated Low

Retrieves historical price data without modifying state or triggering financial transactions.

From the tool's definition Get price history for a prediction market

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs polymarket.market.history safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Apibase, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For polymarket.market.history, this is the rule to start with:

polymarket.market.history Allowed

polymarket.market.history is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "polymarket.market.history": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Apibase, apply this rule, and every polymarket.market.history call is checked against it from then on.

FAQ

Questions about polymarket.market.history

What does the polymarket.market.history tool do? +

Get price history for a prediction market. It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.

What parameters does polymarket.market.history accept? +

polymarket.market.history accepts 3 parameters: days, interval, market_id. Required: market_id. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on polymarket.market.history? +

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

What risk level is polymarket.market.history? +

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

Can I rate-limit polymarket.market.history? +

Yes. Add a rate_limit block to the polymarket.market.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 polymarket.market.history completely? +

Set action: deny in the PolicyLayer policy for polymarket.market.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 polymarket.market.history? +

polymarket.market.history is provided by the Apibase MCP server (apibase-mcp-client). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Apibase, and thousands of servers like it.

This server

All 1384 Apibase tools →

Across the catalogue

The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →