Create a new file with the specified content. Supports nested directories.
AI agents use create_file to create or update resources in Python REPL MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Python REPL MCP Server environment.
This tool creates new files, which is a Write operation (reversible data modification). Severity is high because in the context of a Python REPL server with file system access, an AI agent could create malicious scripts, overwrite critical configuration files, or pollute the file system with unintended content.
From the tool's definition Tool description states 'Create a new file with the specified content.' The verb 'create' and the action of writing content to a new file indicate a reversible data modification operation.
Attacks that exploit this kind of access
Create a new file with the specified content. Supports nested directories. It is categorised as a Write tool in the Python REPL MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Python REPL MCP Server MCP server in PolicyLayer and add a rule for create_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 Python REPL MCP Server. Nothing to install.
create_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_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_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_file is provided by the Python REPL MCP Server MCP server (piplin-es/mcp-python). 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 →