Create a new AutoHotkey v2 script on disk with full path interception support. • Validates .ahk extension (case-insensitive) • Automatically creates parent directories (configurable) • Prevents accidental overwrite unless explicitly allowed • Supports dry-run previews and active file management
AI agents use AHK_File_Create to create or update resources in Ahk — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Ahk environment.
This tool creates files on disk, which is a reversible Write operation. While it has safety features (overwrite prevention, dry-run support), it still modifies the filesystem by creating new scripts. The severity is medium because malicious or erroneous script creation could impact system functionality, but files can be deleted if needed.
From the tool's definition Tool description states it will 'Create a new AutoHotkey v2 script on disk' and 'create parent directories'. The verb 'Create' and the action of writing files to disk are characteristic of Write operations.
Documented attack patterns abuse exactly the kind of access AHK_File_Create gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Ahk, and nothing reaches the server without passing your rules. This is the rule we recommend for AHK_File_Create:
{
"version": "1",
"default": "deny",
"tools": {
"AHK_File_Create": {
"limits": [
{
"counter": "ahk_file_create_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}AHK_File_Create 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 AutoHotkey v2 script on disk with full path interception support. • Validates .ahk extension (case-insensitive) • Automatically creates parent directories (configurable) • Prevents accidental overwrite unless explicitly allowed • Supports dry-run previews and active file management. It is categorised as a Write tool in the Ahk MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Ahk MCP server in PolicyLayer and add a rule for AHK_File_Create: 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 Ahk. Nothing to install.
AHK_File_Create 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 AHK_File_Create 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 AHK_File_Create. 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.
AHK_File_Create is provided by the Ahk MCP server (truecrimedev/ahk-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 40 Ahk tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
40 Ahk tools catalogued and risk-classified — across an index of 42,500+ MCP servers.