create_file
Create a file with specified content on the HexStrike server.
This record as markdown: /tools/hexstrike-ai/create-file.md
What create_file does on Hexstrike Ai
AI agents use create_file to create or update resources in Hexstrike Ai, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Hexstrike Ai environment.
Why create_file is rated Medium
The tool creates files with arbitrary content on a server. While reversible (files can be deleted), this is a Write operation that could be misused to plant malicious payloads, scripts, or configurations on the system. Given the server context (automated pentesting/offensive security tools), severity is high due to potential for establishing persistence, staging attacks, or corrupting legitimate configurations.
From the tool's definition Tool name is 'create_file' and description states it will 'Create a file with specified content on the HexStrike server.' This is file creation/modification without deletion.
Attacks that exploit this kind of access
The rule that runs create_file safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Hexstrike Ai, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For create_file, this is the rule to start with:
create_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.
The button opens the PolicyLayer dashboard: create your workspace, connect Hexstrike Ai, apply this rule, and every create_file call is checked against it from then on.
Questions about create_file
Create a file with specified content on the HexStrike server. It is categorised as a Write tool in the Hexstrike Ai MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Hexstrike Ai 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 Hexstrike Ai. 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 Hexstrike Ai MCP server (0x4m4/hexstrike-ai). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Hexstrike Ai, and thousands of servers like it.
This server
Across the catalogue