Make small edits to files using sed patterns. Efficient for single-line changes, pattern replacements, and simple text transformations.
AI agents use sed_edit to create or update resources in MCP SmallEdit — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your MCP SmallEdit environment.
The tool modifies file content through sed pattern matching and replacements. While these changes are reversible (files can be restored via list_backups/restore_backup functions available on the server), the tool creates or alters data, classifying it as Write rather than Read.
From the tool's definition Tool description states 'Make small edits to files' and 'pattern replacements, and simple text transformations' — these are direct modifications to file content.
Attacks that exploit this kind of access
Make small edits to files using sed patterns. Efficient for single-line changes, pattern replacements, and simple text transformations. It is categorised as a Write tool in the MCP SmallEdit MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the MCP SmallEdit MCP server in PolicyLayer and add a rule for sed_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 SmallEdit. Nothing to install.
sed_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 sed_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 sed_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.
sed_edit is provided by the MCP SmallEdit MCP server (mikeybeez/mcp-smalledit). 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 →