overwrite_lines
AI agents call overwrite_lines to permanently remove resources in TermPipe MCP — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
The name 'overwrite_lines' strongly implies replacing/overwriting existing content in a file, which is an irreversible modification. In a terminal/file management context, overwriting file content cannot be undone. The description is empty, lowering confidence, but the name and server context both point to destructive file modification. Rated high severity given the server's broad terminal and file system access.
From the tool's definition Tool name 'overwrite_lines' on a server that provides 'direct terminal access to execute commands, manage files'; sibling tools include 'append_file' and 'analyze_file_structure', suggesting file manipulation context.
Attacks that exploit this kind of access
overwrite_lines. It is categorised as a Destructive tool in the TermPipe MCP MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the TermPipe MCP server in PolicyLayer and add a rule for overwrite_lines: 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 TermPipe MCP. Nothing to install.
overwrite_lines is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the overwrite_lines 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 overwrite_lines. 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.
overwrite_lines is provided by the TermPipe MCP server (wbind-core/termpipe-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 →