Low Risk

get_detected_flags

获取所有检测到的Flag。

How to control get_detected_flags ↓

AI agents call get_detected_flags to retrieve information from Kali Security MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

This tool retrieves flag data that has already been detected, consistent with Read category operations (search, list, get, fetch). There are no side effects, data modifications, code execution, deletions, or financial transactions. In a CTF/penetration testing context, flags are typically read-only artifacts to be discovered and reported.

From the tool's definition Tool name 'get_detected_flags' and description '获取所有检测到的Flag' (get all detected flags) indicate a retrieval/query operation. The verb 'get' and the passive 'detected' suggest reading already-identified flags without modifying state.

Documented attack patterns abuse exactly the kind of access get_detected_flags gives an agent:

PolicyLayer is an MCP gateway — it sits between your AI agents and Kali Security MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for get_detected_flags:

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

get_detected_flags is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Kali Security MCP — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Go deeper

What does the get_detected_flags tool do? +

获取所有检测到的Flag。. It is categorised as a Read tool in the Kali Security MCP MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_detected_flags? +

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

What risk level is get_detected_flags? +

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

Can I rate-limit get_detected_flags? +

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

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

get_detected_flags is provided by the Kali Security MCP server (seac-25/kali-security-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Kali Security MCP tool call.

Deterministic rules across all 249 Kali Security MCP tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

249 Kali Security MCP tools catalogued and risk-classified — across an index of 42,500+ MCP servers.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.