AI agents use add_phase 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 new data (a phase) in a shared knowledge base used across sessions. While the modification is reversible (distinguishing it from Destructive), it affects project planning state that other agents may depend on. Severity is medium because incorrect phases could mislead planning but won't cause immediate financial or irreversible harm.
From the tool's definition Tool name 'add_phase' and description 'Add a new upcoming phase to the roadmap' indicate creation of new roadmap entries. The action modifies project state by inserting a new phase, which is reversible (phases can be removed or edited).
Documented attack patterns abuse exactly the kind of access add_phase 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 add_phase:
{
"version": "1",
"default": "deny",
"tools": {
"add_phase": {
"limits": [
{
"counter": "add_phase_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}add_phase 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.
Add a new upcoming phase to the roadmap. 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 add_phase: 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.
add_phase 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 add_phase 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 add_phase. 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.
add_phase 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.