multi_edit
AI agents use multi_edit to create or update resources in MCP Claude Code — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your MCP Claude Code environment.
The name 'multi_edit' strongly implies editing/modifying multiple files. Given the server context (file system modifications) and sibling tools like 'edit' and 'content_replace', this tool likely performs batch file edits. Since edits are typically reversible (files can be restored), Write is appropriate. However, if it can overwrite without backup, severity is high.
From the tool's definition Tool name 'multi_edit' on a server described as allowing the AI to 'modify files' and 'direct file system interactions'; sibling tools include 'edit', 'content_replace', suggesting file modification capabilities.
Attacks that exploit this kind of access
multi_edit. It is categorised as a Write tool in the MCP Claude Code MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the MCP Claude Code MCP server in PolicyLayer and add a rule for multi_edit: 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 MCP Claude Code. Nothing to install.
multi_edit 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 multi_edit 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 multi_edit. 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.
multi_edit is provided by the MCP Claude Code MCP server (sdglbl/mcp-claude-code). 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 →