hooks_codemod
Apply a deterministic, $0 (no-LLM) code transform — the real Tier-1 execution path (ADR-143). Supported intents: var-to-const, remove-console, add-logging. Uses the TypeScript compiler with formatting-preserving edits (comments/whitespace survive). Targets: raw
This record as markdown: /tools/ruflo/hooks-codemod.md
What hooks_codemod does on Ruflo
AI agents invoke hooks_codemod to trigger actions in Ruflo. 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.
Why hooks_codemod is rated High
This tool applies automated code transformations directly to source files using the TypeScript compiler. It modifies code in-place (var-to-const, remove-console, add-logging), constituting a write/execute action that alters source code. While the transforms are described as deterministic, the blast radius is high because an AI agent could misuse this to systematically alter codebases.
From the tool's definition Apply a deterministic, $0 (no-LLM) code transform — the real Tier-1 execution path (ADR-143). Uses the TypeScript compiler with formatting-preserving edits. Targets: raw
Attacks that exploit this kind of access
The rule that runs hooks_codemod safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Ruflo, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For hooks_codemod, this is the rule to start with:
hooks_codemod 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Ruflo, apply this rule, and every hooks_codemod call is checked against it from then on.
Questions about hooks_codemod
Apply a deterministic, $0 (no-LLM) code transform — the real Tier-1 execution path (ADR-143). Supported intents: var-to-const, remove-console, add-logging. Uses the TypeScript compiler with formatting-preserving edits (comments/whitespace survive). Targets: raw. It is categorised as a Execute tool in the Ruflo MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Ruflo MCP server in PolicyLayer and add a rule for hooks_codemod: 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 Ruflo. Nothing to install.
hooks_codemod 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 hooks_codemod 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 hooks_codemod. 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.
hooks_codemod is provided by the Ruflo MCP server (ruvnet/ruflo). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Ruflo, and thousands of servers like it.
Across the catalogue