AI agents call market.events.get 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 naming convention (*.get) and server purpose (providing intelligence/signals for trading decisions) strongly suggest this retrieves market event data. No indication of writing, deleting, executing code, or moving financial instruments themselves. However, the empty description reduces confidence. In the context of prediction market tools, 'events' likely refers to market event metadata/information retrieval.
From the tool's definition Tool name 'market.events.get' follows a GET pattern consistent with retrieval operations. Server context involves 'market intelligence' and 'research' which are typically read-only activities. However, description is empty, limiting direct evidence.
Attacks that exploit this kind of access
market.events.get. 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.get: 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.get 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.get 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.get. 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.get 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 →