hooks_post-edit

What hooks_post-edit does on Ruflo

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.

Why hooks_post-edit is rated Medium

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.

The rule that runs hooks_post-edit 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_post-edit, this is the rule to start with:

{
  "version": "1",
  "default": "deny",
  "tools": {
    "hooks_post-edit": {
      "limits": [
        {
          "counter": "hooks_post-edit_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

Questions about hooks_post-edit