AI agents use hooks_post-edit to create or update resources in Ruflo — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Ruflo environment.
This tool records/logs outcomes of edit operations, which constitutes creating or modifying data in a logging/learning system. While it doesn't directly delete or execute arbitrary commands, it writes state and outcomes to storage for learning purposes. Classified as Write rather than Execute because the tool itself records outcomes rather than executing commands (the execution happens elsewhere via Bash hooks).
From the tool's definition Tool name 'hooks_post-edit' and description indicate it 'Record editing outcome for learning' - a write operation that captures and stores editing results. The truncated description mentioning 'native Bash hooks' suggests integration with execution logging.
Attacks that exploit this kind of access
Record editing outcome for learning Use when native Bash hooks (via Claude Code\. It is categorised as a Write tool in the Ruflo MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Ruflo MCP server in PolicyLayer and add a rule for hooks_post-edit: 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_post-edit 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 hooks_post-edit 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_post-edit. 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_post-edit 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.
hooks_post-edit is one line of Ruflo's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →