v3.1.0 M7 Phase C: Approve, reject, or withdraw a pending
AI agents use consensus_resolve to create or update resources in Codevira MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Codevira MCP environment.
This tool creates or modifies data reversibly—it changes the status of pending consensus items from one state to another (approved, rejected, withdrawn). While consequential for project workflow decisions, these changes are reversible (a decision can be reconsidered or superseded, as suggested by the 'consensus_propose_supersession' sibling tool).
From the tool's definition Tool name 'consensus_resolve' combined with description mentioning 'Approve, reject, or withdraw a pending' indicates the tool modifies the state of pending items (likely consensus proposals or phase decisions) by accepting, rejecting, or withdrawing them.
Documented attack patterns abuse exactly the kind of access consensus_resolve gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Codevira MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for consensus_resolve:
{
"version": "1",
"default": "deny",
"tools": {
"consensus_resolve": {
"limits": [
{
"counter": "consensus_resolve_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}consensus_resolve stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
v3.1.0 M7 Phase C: Approve, reject, or withdraw a pending. It is categorised as a Write tool in the Codevira MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Codevira MCP server in PolicyLayer and add a rule for consensus_resolve: 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 Codevira MCP. Nothing to install.
consensus_resolve 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 consensus_resolve 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_resolve. 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_resolve is provided by the Codevira MCP server (sachinshelke/codevira). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Codevira MCP, 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.
48 Codevira MCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.