get_consensus
AI agents call get_consensus to retrieve information from Meridian Edge without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool appears to retrieve or query consensus data from prediction markets without modifying state, executing code, or causing financial transactions directly. It fits the Read category as it fetches aggregated probability data. Severity is low because reading market consensus data poses minimal risk even if misused by an AI agent.
From the tool's definition Tool name 'get_consensus' and server description indicating it 'aggregates probabilities from 27,000+ markets' suggests retrieval of prediction market data.
Attacks that exploit this kind of access
get_consensus. It is categorised as a Read tool in the Meridian Edge MCP Server, which means it retrieves data without modifying state.
Register the Meridian Edge MCP server in PolicyLayer and add a rule for get_consensus: 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 Meridian Edge. Nothing to install.
get_consensus 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 get_consensus 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 get_consensus. 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.
get_consensus is provided by the Meridian Edge MCP server (tmbot12/meridian-edge-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 →