transfer_ipfs-resolve

Resolve IPNS name to CID Use when native package install (

SERVERClaude Flow SOURCEclaude-flow

Critical RISK CLASS

Category Financial

Parameters 00 required

Recommended Approval-gatedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-ruvnet-claude-flow/transfer-ipfs-resolve.md

WHAT IT DOES

What transfer_ipfs-resolve does on Claude Flow

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

RISK

Why transfer_ipfs-resolve is rated Critical

transfer_ipfs-resolve 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

The rule that runs transfer_ipfs-resolve safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Claude Flow, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For transfer_ipfs-resolve, this is the rule to start with:

transfer_ipfs-resolve Approval-gated

Any call to transfer_ipfs-resolve 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": {
    "transfer_ipfs-resolve": {
      "deny_if": [
        {
          "conditions": [],
          "on_deny": "Requires human approval."
        }
      ]
    }
  }
}

GATE THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Claude Flow, apply this rule, and every transfer_ipfs-resolve call is checked against it from then on.

FAQ

Questions about transfer_ipfs-resolve

What does the transfer_ipfs-resolve tool do? +

Resolve IPNS name to CID Use when native package install (. 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 transfer_ipfs-resolve? +

Register the Claude Flow MCP server in PolicyLayer and add a rule for transfer_ipfs-resolve: 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 transfer_ipfs-resolve? +

transfer_ipfs-resolve 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 transfer_ipfs-resolve? +

Yes. Add a rate_limit block to the transfer_ipfs-resolve 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 transfer_ipfs-resolve completely? +

Set action: deny in the PolicyLayer policy for transfer_ipfs-resolve. 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 transfer_ipfs-resolve? +

transfer_ipfs-resolve 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.

KEEP EXPLORING

More on Claude Flow, and thousands of servers like it.

This server

All 496 Claude Flow tools → Critical-risk tools on this server →

Across the catalogue

bridge_transfer on 0xaibridge → All critical-risk MCP tools → The MCP Attack Database →

Guides

Govern MCP payment tools →Human-in-the-loop →Tool call approval →