New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

get_detected_flags

获取所有检测到的Flag。

SERVERKali Security MCP SOURCEseac-25/kali-security-mcp
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/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.

Questions about get_detected_flags

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.

More on Kali Security, and thousands of servers like it.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Kali Security's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.