Save a generated proposal and tasks to a new change
AI agents use openspec_save_proposal 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 creates or stores new proposal and task records in the OpenSpec system. It modifies system state by adding new data but does not delete, execute external code, or trigger financial transactions. The reversible nature (evidenced by sibling archive/update capabilities) places it in Write rather than Destructive.
From the tool's definition Tool name 'openspec_save_proposal' and description 'Save a generated proposal and tasks to a new change' indicate creation of new data records (proposals and tasks).
Documented attack patterns abuse exactly the kind of access openspec_save_proposal 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_save_proposal:
{
"version": "1",
"default": "deny",
"tools": {
"openspec_save_proposal": {
"limits": [
{
"counter": "openspec_save_proposal_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
} openspec_save_proposal 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.
Save a generated proposal and tasks to a new change. 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_save_proposal: 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_save_proposal 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_save_proposal 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_save_proposal. 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_save_proposal 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.