aidefence_is_safe

Quick boolean check if input is safe. Fastest option for simple validation. Use when nothing native exists — Claude Code does not have a PII / prompt-injection / adversarial-text scanner. Pair with any tool that ingests untrusted input (browser scrape, federation envelope, memory_import_claude).

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/aidefence-is-safe.md

WHAT IT DOES

What aidefence_is_safe does on Claude Flow

AI agents call aidefence_is_safe 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 aidefence_is_safe is rated Low

This tool queries or evaluates input data to determine safety status without modifying, creating, deleting, or executing external operations. It is purely an informational check that returns a boolean value. The blast radius of misuse is minimal since it only informs decisions rather than directly effecting changes. Classification as Read is appropriate for a validation/scanning function.

From the tool's definition Tool performs a "Quick boolean check if input is safe" and is described as a validation scanner for PII/prompt-injection/adversarial-text detection. It returns a boolean result with no side effects mentioned.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

aidefence_is_safe Allowed

aidefence_is_safe 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": {
    "aidefence_is_safe": {}
  }
}

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 aidefence_is_safe call is checked against it from then on.

FAQ

Questions about aidefence_is_safe

What does the aidefence_is_safe tool do? +

How do I enforce a policy on aidefence_is_safe? +

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

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

Can I rate-limit aidefence_is_safe? +

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

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

aidefence_is_safe 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

The MCP Attack Database →

Guides

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