Delete the contents of a text file.
AI agents call delete_text_file_contents to permanently remove resources in Mcp Text Editor — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Deletion of file contents cannot be undone and represents data loss. While not a file deletion per se, clearing all contents of a file is a destructive operation that warrants the Destructive category over Write. Severity is high because an AI agent misusing this could eliminate important data, though the blast radius is somewhat limited to a single file's contents rather than an entire filesystem or database.
From the tool's definition Tool name is 'delete_text_file_contents' and description states 'Delete the contents of a text file.' This directly removes data from a file irreversibly.
Documented attack patterns abuse exactly the kind of access delete_text_file_contents gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Mcp Text Editor, and nothing reaches the server without passing your rules. This is the rule we recommend for delete_text_file_contents:
{
"version": "1",
"default": "deny",
"hide": [
"delete_text_file_contents"
]
}delete_text_file_contents disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.
Free to start. No card required.
Delete the contents of a text file. It is categorised as a Destructive tool in the Mcp Text Editor MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Mcp Text Editor MCP server in PolicyLayer and add a rule for delete_text_file_contents: 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 Text Editor. Nothing to install.
delete_text_file_contents 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 delete_text_file_contents 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 delete_text_file_contents. 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.
delete_text_file_contents is provided by the Mcp Text Editor MCP server (tumf/mcp-text-editor). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 6 Mcp Text Editor tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
6 Mcp Text Editor tools catalogued and risk-classified — across an index of 42,500+ MCP servers.