Update an existing revision, usually to add metadata or correct information.
AI agents use openspec_update_revision to create or update resources in OpenSpec MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your OpenSpec MCP environment.
This tool modifies existing data (revisions) in a reversible manner—updates to metadata or corrections can typically be undone or revised further. It does not delete data (which would be Destructive), execute arbitrary code (Execute), or involve financial transactions (Financial). The presence of 'approval workflows' in the server description suggests write operations may be gated, reducing blast radius.
From the tool's definition Tool description states 'Update an existing revision, usually to add metadata or correct information.' The verb 'update' and the explicit mention of modifying existing data indicates write capability.
Documented attack patterns abuse exactly the kind of access openspec_update_revision gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and OpenSpec MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for openspec_update_revision:
{
"version": "1",
"default": "deny",
"tools": {
"openspec_update_revision": {
"limits": [
{
"counter": "openspec_update_revision_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}openspec_update_revision 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 an existing revision, usually to add metadata or correct information. It is categorised as a Write tool in the OpenSpec MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the OpenSpec MCP server in PolicyLayer and add a rule for openspec_update_revision: 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 OpenSpec MCP. Nothing to install.
openspec_update_revision 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 openspec_update_revision 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 openspec_update_revision. 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.
openspec_update_revision is provided by the OpenSpec MCP server (lumiaqian/openspec-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from OpenSpec 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.
40 OpenSpec MCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.