Create a ZIP containing selected changed files and generated markdown reports.
AI agents use mcp_create_change_zip to create or update resources in Local Code — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Local Code environment.
The tool creates new output files (ZIP archives with changed files and markdown reports) but does not delete, modify original sources irreversibly, or execute arbitrary code. It aggregates and exports existing data. This is a Write operation rather than Read because it generates and stores new artifacts.
From the tool's definition Creates a ZIP file containing selected changed files and generated markdown reports. The tool packages existing data into a new artifact (archive file), which is a reversible write operation.
Attacks that exploit this kind of access
Create a ZIP containing selected changed files and generated markdown reports. It is categorised as a Write tool in the Local Code MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Local Code MCP server in PolicyLayer and add a rule for mcp_create_change_zip: 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 Local Code. Nothing to install.
mcp_create_change_zip 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 mcp_create_change_zip 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 mcp_create_change_zip. 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.
mcp_create_change_zip is provided by the Local Code MCP server (js190-prog/local-code-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →