AI agents call market.events.trending 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.
This tool retrieves and presents trending market event information without modifying, deleting, or executing any operations. It is a pure data retrieval function analogous to a search or list operation. While the broader server context involves prediction markets and trading, this specific tool only gathers intelligence data to inform decisions rather than executing trades, moving funds, or modifying any state.
From the tool's definition Tool name 'market.events.trending' combined with description 'Get top trending prediction market events' indicates a retrieval operation.
Attacks that exploit this kind of access
Get top trending prediction market events. 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.trending: 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.trending 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.trending 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.trending. 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.trending 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 →