conclave_config
AI agents use conclave_config to create or update resources in Conclave MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Conclave MCP environment.
The naming pattern strongly implies this tool modifies conclave configuration parameters (model selection, ranking methods, consensus rules, etc.). Configuration changes are reversible (Write, not Destructive), but could redirect LLM queries to malicious models or alter consensus logic if misconfigured by an agent without proper guardrails.
From the tool's definition Tool name 'conclave_config' suggests configuration modification. The empty description prevents direct verification, but 'config' typically indicates Write operations that modify settings or state.
Attacks that exploit this kind of access
conclave_config. It is categorised as a Write tool in the Conclave MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Conclave MCP server in PolicyLayer and add a rule for conclave_config: 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_config is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the conclave_config 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_config. 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_config 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 →