AI agents call market.events.analysis 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.
The tool appears to perform analysis on market events, which falls under data retrieval and querying rather than modification, execution, or destruction. However, the empty description creates uncertainty. Context from sibling tools (analytics.performance, analytics.report, market.data.get, market.data.history, market.data.list) all suggest read-heavy data retrieval patterns.
From the tool's definition Tool name 'market.events.analysis' suggests analysis of market events, consistent with the server's stated purpose of providing 'prediction market intelligence, research, and strategy signals.' The '.analysis' suffix indicates a read-only analytical operation…
Attacks that exploit this kind of access
market.events.analysis. It is categorised as a Read tool in the Rekko MCP MCP Server, which means it retrieves data without modifying state.
Register the Rekko MCP server in PolicyLayer and add a rule for market.events.analysis: 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.
market.events.analysis 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 market.events.analysis 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 market.events.analysis. 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.
market.events.analysis 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.
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 →