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

issue_vulnerability

A execute tool on the Kali Security MCP server.

SERVERKali Security MCP SOURCEseac-25/kali-security-mcp
High RISK CLASS
Category Execute
Parameters 00 required
Recommended Rate-limitedsee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/seac-25-kali-security-mcp/issue-vulnerability.md

What issue_vulnerability does on Kali Security MCP

AI agents invoke issue_vulnerability to trigger actions in Kali Security MCP. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.

Why issue_vulnerability is rated High

The description is empty, lowering confidence. However, the server context (Kali Linux security tools, penetration testing) and sibling tools (ad_full_attack, adaptive_network_penetration, adaptive_sqli_test) strongly suggest this tool executes or triggers vulnerability-related actions.

From the tool's definition Tool name 'issue_vulnerability' on a server described as integrating 193 Kali Linux security tools for penetration testing and vulnerability assessment. Description is empty.

Questions about issue_vulnerability

What does the issue_vulnerability tool do? +

issue_vulnerability is a execute tool on the Kali Security MCP server. It is categorised as a Execute tool in the Kali Security MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on issue_vulnerability? +

Register the Kali Security MCP server in PolicyLayer and add a rule for issue_vulnerability: 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 issue_vulnerability? +

issue_vulnerability is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit issue_vulnerability? +

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

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

issue_vulnerability 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.