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

cve_search

A execute tool on the Zebbern Kali MCP server.

SERVERZebbern Kali MCP SOURCEzebbern/zebbern-kali-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/zebbern-zebbern-kali-mcp/cve-search.md

What cve_search does on Zebbern Kali MCP

AI agents invoke cve_search to trigger actions in Zebbern Kali 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 cve_search is rated High

The description is empty, lowering confidence. However, given the server context (Kali Linux pentest toolkit, Docker-based, AI agent access) and sibling tools that are all offensive security tools, 'cve_search' likely queries or executes CVE lookups and potentially exploit searches. On a Kali-based system, this could invoke tools like searchsploit or similar that query vulnerability databases.

From the tool's definition Tool name 'cve_search' on a Kali Linux penetration testing MCP server with sibling tools including ad_secretsdump, ad_psexec, ad_password_spray, and ad_wmiexec

Questions about cve_search

What does the cve_search tool do? +

cve_search is a execute tool on the Zebbern Kali MCP server. It is categorised as a Execute tool in the Zebbern Kali 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 cve_search? +

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

What risk level is cve_search? +

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

Can I rate-limit cve_search? +

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

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

cve_search is provided by the Zebbern Kali MCP server (zebbern/zebbern-kali-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

More on Zebbern Kali, 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 Zebbern Kali'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.