market.data.history

market.data.history

Server Rekko MCP rekko-ai/rekko-mcp
Category Read
Risk class Low
Parameters 00 required

What market.data.history does on Rekko MCP

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

Why market.data.history needs a policy

This tool retrieves historical market data for analysis and research purposes. While the description is empty, the naming convention and server context (providing 'market intelligence, research, and strategy signals') strongly suggest a read-only data retrieval function. However, confidence is reduced to 0.75 due to missing description.

From the tool's definition Tool name 'market.data.history' and context of prediction market intelligence platform indicates retrieval of historical market data. Sibling tools include 'market.data.get' and 'market.data.list' which are clearly Read operations.

Questions about market.data.history

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

market.data.history. It is categorised as a Read tool in the Rekko MCP MCP Server, which means it retrieves data without modifying state.

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

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

What risk level is market.data.history? +

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

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

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

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

market.data.history is provided by the Rekko MCP server (rekko-ai/rekko-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.