Low Risk

aikido_explain

Get a detailed explanation of a specific Aikido security detector, including what it checks, why it matters, and remediation guidance.

Part of the Aikido server.

aikido_explain is read-only, but an agent in a loop can still rack up calls and cost. PolicyLayer caps every call before it runs. Live in minutes.

SECURE AIKIDO →

Free to start. No card required.

AI agents call aikido_explain to retrieve information from Aikido without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.

Even though aikido_explain only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.

Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "aikido_explain": {}
  }
}

See the full Aikido policy for all 4 tools.

Get this rule live on your own Aikido server in minutes. PolicyLayer enforces it on every call, before it runs.

ENFORCE ON MY AIKIDO →

These attack patterns abuse exactly the kind of access aikido_explain gives an agent. Each links to the full case and the policy that stops it:

Browse the full MCP Attack Database →

Every attack above starts with a tool call. PolicyLayer checks each one against your policy first, so aikido_explain only ever does what you allow.

SECURE AIKIDO →

Other read tools across the catalogue. The same approach applies to each: allow, with a rate cap to control cost.

What does the aikido_explain tool do? +

Get a detailed explanation of a specific Aikido security detector, including what it checks, why it matters, and remediation guidance.. It is categorised as a Read tool in the Aikido MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on aikido_explain? +

Register the Aikido MCP server in PolicyLayer and add a rule for aikido_explain: 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 Aikido. Nothing to install.

What risk level is aikido_explain? +

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

Can I rate-limit aikido_explain? +

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

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

aikido_explain is provided by the Aikido MCP server (aikido-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Aikido tool call.

Deterministic rules across all 4 Aikido tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

4,600+ MCP servers and 31,000+ tools scanned and risk-classified.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.