Query 3-7 models and aggregate responses using voting strategy (majority/supermajority/unanimous). Returns consensus answer with confidence score.
AI agents invoke consensus to trigger actions in HydraMCP. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
This tool executes queries against multiple LLM models simultaneously and aggregates their responses. It triggers external operations (API calls to multiple cloud/local LLMs) whose effects depend on the arguments passed. It is not purely Read because it orchestrates parallel external model invocations and applies a voting/aggregation strategy.
From the tool's definition Query 3-7 models and aggregate responses using voting strategy (majority/supermajority/unanimous). Returns consensus answer with confidence score.
Documented attack patterns abuse exactly the kind of access consensus gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and HydraMCP, and nothing reaches the server without passing your rules. This is the rule we recommend for consensus:
{
"version": "1",
"default": "deny",
"tools": {
"consensus": {
"limits": [
{
"counter": "consensus_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}consensus stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Query 3-7 models and aggregate responses using voting strategy (majority/supermajority/unanimous). Returns consensus answer with confidence score. It is categorised as a Execute tool in the HydraMCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Hydra MCP server in PolicyLayer and add a rule for 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 HydraMCP. Nothing to install.
consensus is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the 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 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.
consensus is provided by the Hydra MCP server (pickle-pixel/hydramcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from HydraMCP, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
8 HydraMCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.