propose_patch
Submit a multi-file apply_patch envelope fixing the root cause while preserving legitimate behavior. Do not weaken tests or alter the frozen probe.
This record as markdown: /tools/0sec/propose-patch.md
What propose_patch does on 0sec
AI agents use propose_patch to create or update resources in 0sec, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your 0sec environment.
Why propose_patch is rated Medium
Modifies code files reversibly through patch application; moderate blast radius if misapplied to production systems.
From the tool's definition Submit multi-file apply_patch envelope fixing root cause preserving legitimate behavior.
Risk signalsAdmin/system-level operation
Attacks that exploit this kind of access
The rule that runs propose_patch safely
PolicyLayer is an MCP gateway: it sits between your AI agents and 0sec, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For propose_patch, this is the rule to start with:
propose_patch 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.
The button opens the PolicyLayer dashboard: create your workspace, connect 0sec, apply this rule, and every propose_patch call is checked against it from then on.
Questions about propose_patch
Submit a multi-file apply_patch envelope fixing the root cause while preserving legitimate behavior. Do not weaken tests or alter the frozen probe. It is categorised as a Write tool in the 0sec MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the 0sec MCP server in PolicyLayer and add a rule for propose_patch: 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 0sec. Nothing to install.
propose_patch 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 propose_patch 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 propose_patch. 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.
propose_patch is provided by the 0sec MCP server (0sec-labs/0sec). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on 0sec, and thousands of servers like it.
This server
Across the catalogue