conclave_ranked
AI agents invoke conclave_ranked to trigger actions in Conclave MCP. 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.
Based on sibling tools and server description, this tool likely executes ranked evaluations by consulting multiple frontier LLM APIs (GPT, Claude, Gemini, Grok, DeepSeek), which constitutes triggering external operations. The description is empty, lowering confidence.
From the tool's definition Tool name 'conclave_ranked' and server context referencing 'peer-ranked evaluations' suggest this triggers LLM queries and ranking operations across multiple external AI models.
Attacks that exploit this kind of access
conclave_ranked. It is categorised as a Execute tool in the Conclave MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Conclave MCP server in PolicyLayer and add a rule for conclave_ranked: 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 Conclave MCP. Nothing to install.
conclave_ranked 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 conclave_ranked 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 conclave_ranked. 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.
conclave_ranked is provided by the Conclave MCP server (stephenpeters/conclave-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 →