cve_set_vuln_ignore
Ignore a specific vulnerability permanently.
This record as markdown: /tools/aapanel-mcp/cve-set-vuln-ignore.md
What cve_set_vuln_ignore does on Aapanel
AI agents call cve_set_vuln_ignore to permanently remove resources in Aapanel, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why cve_set_vuln_ignore is rated Critical
Permanently ignoring a vulnerability is an irreversible security action — it suppresses future alerts and remediation prompts for that CVE indefinitely. The word 'permanently' indicates this cannot be undone without deliberate re-configuration. Misuse by an AI agent could leave critical security flaws unaddressed across a server environment.
From the tool's definition Ignore a specific vulnerability permanently
Attacks that exploit this kind of access
The rule that runs cve_set_vuln_ignore safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Aapanel, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For cve_set_vuln_ignore, this is the rule to start with:
cve_set_vuln_ignore is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Aapanel, apply this rule, and every cve_set_vuln_ignore call is checked against it from then on.
Questions about cve_set_vuln_ignore
Ignore a specific vulnerability permanently. It is categorised as a Destructive tool in the Aapanel MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Aapanel MCP server in PolicyLayer and add a rule for cve_set_vuln_ignore: 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 Aapanel. Nothing to install.
cve_set_vuln_ignore is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the cve_set_vuln_ignore 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 cve_set_vuln_ignore. 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.
cve_set_vuln_ignore is provided by the Aapanel MCP server (nipunanirmal/aapanel-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Aapanel, and thousands of servers like it.
Across the catalogue