AI agents use edit to create or update resources in Claude Context Local — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Claude Context Local environment.
The tool name 'edit' strongly suggests file or content modification. Without a description, I cannot confirm if this is reversible or destructive, so I classify it conservatively as Write rather than Destructive. The lack of documentation lowers confidence to 0.75.
From the tool's definition Tool named 'edit' with no description provided. Given the sibling tools (add_codebase, read_file, search_codebase), this server operates on local codebases. An 'edit' tool in this context most likely modifies files or codebase content.
Documented attack patterns abuse exactly the kind of access edit gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Claude Context Local, and nothing reaches the server without passing your rules. This is the rule we recommend for edit:
{
"version": "1",
"default": "deny",
"tools": {
"edit": {
"limits": [
{
"counter": "edit_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}edit 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.
edit. It is categorised as a Write tool in the Claude Context Local MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Claude Context Local MCP server in PolicyLayer and add a rule for 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 Claude Context Local. Nothing to install.
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 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 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.
edit is provided by the Claude Context Local MCP server (mikeo-ai/claude-context-local). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Claude Context Local, 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.
9 Claude Context Local tools catalogued and risk-classified — across an index of 43,000+ MCP servers.