Provides LSP-like analysis and auto-fixing for AutoHotkey v2 code. Accepts direct code or a file path (falls back to active file).
AI agents invoke AHK_LSP to trigger actions in Ahk. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
The tool performs both analysis (Read) and auto-fixing (Write/Execute) of AutoHotkey v2 code. The 'auto-fixing' capability means it can modify source code files, which elevates it beyond pure Read. Since it operates on an AHK execution server with code execution capabilities and can alter code, the most severe applicable category is Execute/Write.
From the tool's definition 'LSP-like analysis and auto-fixing for AutoHotkey v2 code' — the auto-fixing aspect modifies code, and the tool operates within an execution-capable AHK environment
Documented attack patterns abuse exactly the kind of access AHK_LSP 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_LSP:
{
"version": "1",
"default": "deny",
"tools": {
"AHK_LSP": {
"limits": [
{
"counter": "ahk_lsp_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}AHK_LSP stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Provides LSP-like analysis and auto-fixing for AutoHotkey v2 code. Accepts direct code or a file path (falls back to active file). It is categorised as a Execute tool in the Ahk MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Ahk MCP server in PolicyLayer and add a rule for AHK_LSP: 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_LSP is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the AHK_LSP 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_LSP. 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_LSP 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.