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).
This record as markdown: /tools/ruflo/aidefence-is-safe.md
What aidefence_is_safe does on Ruflo
AI agents call aidefence_is_safe to retrieve information from Ruflo without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why aidefence_is_safe is rated Low
This is a validation/analysis tool that reads input and returns a safety assessment. It does not create, modify, delete, execute code, or transfer money. The description explicitly positions it as a scanner for detecting unsafe content (PII, prompt injection, adversarial text), which is inherently a read operation.
From the tool's definition Tool performs a 'Quick boolean check if input is safe' — it queries/validates input and returns a boolean result with no side effects, modifications, or external state changes.
Attacks that exploit this kind of access
The rule that runs aidefence_is_safe safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Ruflo, 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 is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Ruflo, apply this rule, and every aidefence_is_safe call is checked against it from then on.
Questions about 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). It is categorised as a Read tool in the Ruflo MCP Server, which means it retrieves data without modifying state.
Register the Ruflo 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 Ruflo. Nothing to install.
aidefence_is_safe is a Read tool with low risk. Read-only tools are generally safe to allow by default.
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.
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.
aidefence_is_safe is provided by the Ruflo MCP server (ruvnet/ruflo). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Ruflo, and thousands of servers like it.
This server
Across the catalogue