Low Risk

cve_package_audit

cve_package_audit

How to control cve_package_audit ↓

AI agents call cve_package_audit to retrieve information from Zebbern Kali MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

CVE package auditing is a read-only reconnaissance activity that retrieves vulnerability data about installed packages without modifying systems or executing exploits. However, severity is high because in a Kali Linux penetration testing context with sibling tools like ad_psexec and ad_secretsdump, reconnaissance data gathered here could directly enable follow-on attacks.

From the tool's definition Tool name 'cve_package_audit' indicates a scanning/auditing function that identifies CVEs in packages. The empty description limits certainty, but the naming pattern aligns with vulnerability assessment rather than active exploitation.

Documented attack patterns abuse exactly the kind of access cve_package_audit gives an agent:

PolicyLayer is an MCP gateway — it sits between your AI agents and Zebbern Kali MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for cve_package_audit:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "cve_package_audit": {}
  }
}

cve_package_audit is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Zebbern Kali MCP — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Go deeper

What does the cve_package_audit tool do? +

cve_package_audit. It is categorised as a Read tool in the Zebbern Kali MCP MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on cve_package_audit? +

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

cve_package_audit is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit cve_package_audit? +

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

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

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

Enforce policy on every Zebbern Kali MCP tool call.

Deterministic rules across all 128 Zebbern Kali MCP tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

128 Zebbern Kali MCP tools catalogued and risk-classified — across an index of 42,500+ MCP servers.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.