Update the current phase status: pending | in_progress | blocked.
AI agents use update_phase_status 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 by updating phase status in the shared knowledge base. While it changes project state, the operation is reversible (status can be changed again), making it Write rather than Destructive. Severity is medium because incorrect status updates could mislead an AI agent about project progress, but the impact is limited to metadata rather than deletion or financial harm.
From the tool's definition Tool name 'update_phase_status' and description 'Update the current phase status' indicates modification of phase state data. The allowed values (pending | in_progress | blocked) are state transitions that change stored project context.
Documented attack patterns abuse exactly the kind of access update_phase_status 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 update_phase_status:
{
"version": "1",
"default": "deny",
"tools": {
"update_phase_status": {
"limits": [
{
"counter": "update_phase_status_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}update_phase_status 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.
Update the current phase status: pending | in_progress | blocked. 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 update_phase_status: 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.
update_phase_status 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 update_phase_status 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 update_phase_status. 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.
update_phase_status 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.