attack_coverage
ATT&CK technique label coverage for task findings (report appendix; not a runtime driver).
This record as markdown: /tools/seac-25-kali-security-mcp/attack-coverage.md
What attack_coverage does on Kali Security MCP
AI agents call attack_coverage 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 attack_coverage is rated Low
Retrieves and reports ATT&CK technique coverage data without executing attacks or modifying systems.
From the tool's definition coverage for task findings; not a runtime driver; report appendix
Attacks that exploit this kind of access
The rule that runs attack_coverage 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 attack_coverage, this is the rule to start with:
attack_coverage 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 attack_coverage call is checked against it from then on.
Questions about attack_coverage
ATT&CK technique label coverage for task findings (report appendix; not a runtime driver). 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 attack_coverage: 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.
attack_coverage 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 attack_coverage 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 attack_coverage. 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.
attack_coverage 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