AI agents use create_text_file to create or update resources in Mcp Text Editor — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Mcp Text Editor environment.
Creating a new file is a write operation that modifies the filesystem by adding content, but is reversible since the file can be deleted. The severity is medium rather than low because uncontrolled file creation could fill disk space, create unexpected files in sensitive locations, or overwrite existing files if the tool permits it. The confidence is high based on the clear and direct description.
From the tool's definition Tool name 'create_text_file' and description 'Create a new text file' indicate file creation. Sibling tools include destructive operations (delete_text_file_contents), but this tool itself performs reversible file creation.
Documented attack patterns abuse exactly the kind of access create_text_file 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 create_text_file:
{
"version": "1",
"default": "deny",
"tools": {
"create_text_file": {
"limits": [
{
"counter": "create_text_file_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}create_text_file 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.
Create a new text file. It is categorised as a Write tool in the Mcp Text Editor MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Mcp Text Editor MCP server in PolicyLayer and add a rule for create_text_file: 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.
create_text_file 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 create_text_file 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 create_text_file. 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.
create_text_file 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.