This record as markdown: /tools/seac-25-kali-security-mcp/get-detected-flags.md
What get_detected_flags does on Kali Security MCP
AI agents call get_detected_flags to retrieve information from Kali Security MCP without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why get_detected_flags is rated Low
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.
Attacks that exploit this kind of access
The rule that runs get_detected_flags safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Kali Security MCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_detected_flags, this is the rule to start with:
get_detected_flags 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 Kali Security MCP, apply this rule, and every get_detected_flags call is checked against it from then on.
Questions about get_detected_flags
获取所有检测到的Flag。. It is categorised as a Read tool in the Kali Security MCP MCP Server, which means it retrieves data without modifying state.
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.
get_detected_flags 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 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.
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.
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.
More on Kali Security, and thousands of servers like it.
This server
Across the catalogue