hooks_pre-task
Record task start and get agent suggestions with intelligent model routing (ADR-026) Use when native Bash hooks (via Claude Code\
This record as markdown: /tools/ruflo/hooks-pre-task.md
What hooks_pre-task does on Ruflo
AI agents invoke hooks_pre-task 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_pre-task is rated High
This tool executes code at task initiation points and routes to agent models. While the description is truncated and incomplete ('Use when native Bash hooks (via Claude Code\'), the mention of Bash hooks and task execution clearly places this in the Execute category. The potential to run arbitrary shell commands through hook mechanisms and influence agent behavior gives it a high severity rating.
From the tool's definition The tool 'hooks_pre-task' records task start and involves 'intelligent model routing' and integration with 'native Bash hooks (via Claude Code'. The description indicates execution of task hooks and routing logic that can trigger agent actions.
Attacks that exploit this kind of access
The rule that runs hooks_pre-task 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_pre-task, this is the rule to start with:
hooks_pre-task 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_pre-task call is checked against it from then on.
Questions about hooks_pre-task
Record task start and get agent suggestions with intelligent model routing (ADR-026) Use when native Bash hooks (via Claude Code\. 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_pre-task: 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_pre-task 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_pre-task 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_pre-task. 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_pre-task 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