transfer_store-info

Get detailed info about a pattern Use when native package install (

SERVERClaude Flow SOURCEclaude-flow

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

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

WHAT IT DOES

What transfer_store-info does on Claude Flow

AI agents call transfer_store-info to retrieve information from Claude Flow without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why transfer_store-info is rated Low

The description says 'Get detailed info about a pattern', which is a read/query operation. However, the description is incomplete and truncated ('Use when native package install ('), which lowers confidence. The tool name 'transfer_store-info' is somewhat ambiguous but combined with the partial description suggests a read operation to retrieve stored pattern information.

From the tool's definition 'Get detailed info about a pattern' — retrieves information only; no side effects described

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs transfer_store-info 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_store-info, this is the rule to start with:

transfer_store-info Allowed

transfer_store-info is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "transfer_store-info": {}
  }
}

ALLOW ONLY 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_store-info call is checked against it from then on.

FAQ

Questions about transfer_store-info

What does the transfer_store-info tool do? +

Get detailed info about a pattern Use when native package install (. It is categorised as a Read tool in the Claude Flow MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on transfer_store-info? +

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

transfer_store-info is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit transfer_store-info? +

Yes. Add a rate_limit block to the transfer_store-info 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_store-info completely? +

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

transfer_store-info 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 →

Across the catalogue

get_team_info on CTFtime MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →