hooks_transfer · Claude Flow MCP: Risk & Policy

WHAT IT DOES

What hooks_transfer does on Claude Flow

AI agents use hooks_transfer to commit financial operations through Claude Flow — usually the final step of a payment, billing, or trading workflow. A call moves real money.

WHY IT NEEDS A POLICY

Why hooks_transfer needs a policy

hooks_transfer moves real money, and an autonomous agent will call it with the same confidence it calls a search tool. A misread instruction or an injected prompt is all it takes to drain an account or blow a budget.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

hooks_transfer Approval-gated

Any call to hooks_transfer is blocked until a human approves it. The rest of the server keeps working.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "hooks_transfer": {
      "deny_if": [
        {
          "conditions": [],
          "on_deny": "Requires human approval."
        }
      ]
    }
  }
}

GATE THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Claude Flow, so you can run agents against it safely.

FAQ

Questions about hooks_transfer

What does the hooks_transfer tool do? +

Transfer learned patterns from another project Use when native Bash hooks (via Claude Code\. It is categorised as a Financial tool in the Claude Flow MCP Server, which means it involves financial transactions. Block by default and require explicit approval.

How do I enforce a policy on hooks_transfer? +

Register the Claude Flow MCP server in PolicyLayer and add a rule for hooks_transfer: 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 Claude Flow. Nothing to install.

What risk level is hooks_transfer? +

hooks_transfer is a Financial tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit hooks_transfer? +

Yes. Add a rate_limit block to the hooks_transfer 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.

How do I block hooks_transfer completely? +

Set action: deny in the PolicyLayer policy for hooks_transfer. 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.

What MCP server provides hooks_transfer? +

hooks_transfer is provided by the Claude Flow MCP server (claude-flow). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.