create_file
Create a file with specified content on the API server.
This record as markdown: /tools/nyxstrike/create-file.md
What create_file does on Nyxstrike
AI agents use create_file to create or update resources in Nyxstrike, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Nyxstrike environment.
Why create_file is rated Medium
The tool creates files on a remote server, which is a reversible modification of data/state. While file creation is generally Write-category, the severity is elevated to 'high' because: (1) it operates on an 'API server' in a penetration testing platform context, (2) malicious file creation could enable code execution or persistence attacks, and (3) the server context (Nyxstrike - offensive security) suggests…
From the tool's definition Tool description states 'Create a file with specified content on the API server.' This is a write operation that creates new files.
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 Nyxstrike, 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 Nyxstrike, 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 API server. It is categorised as a Write tool in the Nyxstrike MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Nyxstrike 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 Nyxstrike. 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 Nyxstrike MCP server (CommonHuman-Lab/nyxstrike). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Nyxstrike, and thousands of servers like it.
This server
Across the catalogue