get_market_history

THE RISK

Low Risk

Why get_market_history needs a policy

This tool queries and retrieves historical market data from Polymarket prediction markets. It is purely a read operation that returns existing data without creating, modifying, deleting, or executing external actions. The 'EXPERIMENTAL' label does not change the functional classification.

From the tool's definition Tool name is 'get_market_history' and description states 'Get historical market data for a specific market' — retrieves past data with no modification or side effects.

Documented attack patterns abuse exactly the kind of access get_market_history gives an agent:

POLICY

How to control get_market_history

PolicyLayer is an MCP gateway — it sits between your AI agents and Polymarket, and nothing reaches the server without passing your rules. This is the rule we recommend for get_market_history:

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_market_history": {}
  }
}

get_market_history is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

Create a free account and register Polymarket — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

CAP THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Polymarket tools

Read get_event_by_id Get detailed information about a specific event by its ID. Read get_events Get a list of all available events on Polymarket with comprehensive filtering options. Read get_market_by_id Get detailed information about a specific market by its ID. Read get_markets Get a list of all available markets on Polymarket with comprehensive filtering options. Read get_order_book [EXPERIMENTAL] Get the current order book for a specific market. Read get_recent_trades [EXPERIMENTAL] Get the latest trades for a specific market. Read search_markets Search for markets by keyword or phrase using slug filtering.

All 8 Polymarket tools →

Read tools on other servers

M-Team MCP Server get_torrent_detail YouTube MCP Server search_channel Android Forensics ADB MCP Server parse_browser_history 0xarchive web3_challenge

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Data exfiltration → How read access becomes an exfiltration channel when chained with untrusted content.
MCP token cost → What connecting this server costs in context-window tokens on every request.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about get_market_history

What does the get_market_history tool do? +

[EXPERIMENTAL] Get historical market data for a specific market. It is categorised as a Read tool in the Polymarket MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_market_history? +

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

What risk level is get_market_history? +

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

Can I rate-limit get_market_history? +

Yes. Add a rate_limit block to the get_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 get_market_history completely? +

Set action: deny in the PolicyLayer policy for get_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 get_market_history? +

get_market_history is provided by the Polymarket MCP server (pab1it0/polymarket-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Polymarket tool call.

Start from Polymarket, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →