my-tool

My custom tool

SERVERClaude Flow SOURCEclaude-flow

Low RISK CLASS

Category Other

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-ruvnet-claude-flow/my-tool.md

WHAT IT DOES

What my-tool does on Claude Flow

AI agents call my-tool as a supporting operation in Claude Flow workflows.

RISK

Why my-tool is rated Low

The tool name and description provide no meaningful information about what the tool does, what data it accesses, or what side effects it may have. With no actionable evidence, no specific risk category can be reliably assigned. Confidence is very low; the classification should be revisited once a proper description is available.

From the tool's definition Tool name: 'my-tool', description: 'My custom tool' — both are entirely generic and uninformative.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

my-tool Rate-limited

my-tool gets a rate cap, and everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "my-tool": {
      "limits": [
        {
          "counter": "my-tool_rate",
          "window": "minute",
          "max": 60,
          "scope": "grant"
        }
      ]
    }
  }
}

SET A RULE FOR THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about my-tool

What does the my-tool tool do? +

My custom tool. It is categorised as a Other tool in the Claude Flow MCP Server, which means it performs auxiliary operations.

How do I enforce a policy on my-tool? +

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

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

Can I rate-limit my-tool? +

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

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

my-tool 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

async_tool on Enhanced Image Analysis MCP Server →async_tool on Agent Jail →my_tool on Agentic Automl Platform → The MCP Attack Database →

Guides

Roll out MCP under one policy →Tool risk categories →MCP tool →