Record one architectural decision. Set do_not_revert=true to
AI agents use record_decision 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 decision records in a shared knowledge base without irreversible deletion. While it affects architectural state, it is reversible (decisions can be updated or superseded, as evidenced by sibling tools like 'consensus_propose_supersession' and 'consensus_resolve').
From the tool's definition Tool name 'record_decision' and description 'Record one architectural decision' indicate creation/modification of decision records in a persistent knowledge base.
Documented attack patterns abuse exactly the kind of access record_decision 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 record_decision:
{
"version": "1",
"default": "deny",
"tools": {
"record_decision": {
"limits": [
{
"counter": "record_decision_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}record_decision 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.
Record one architectural decision. Set do_not_revert=true to. 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 record_decision: 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.
record_decision 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 record_decision 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 record_decision. 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.
record_decision 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.