cve_set_ignore
Ignore/dismiss a CVE vulnerability finding.
This record as markdown: /tools/aapanel-mcp/cve-set-ignore.md
What cve_set_ignore does on Aapanel
AI agents use cve_set_ignore to create or update resources in Aapanel, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Aapanel environment.
Why cve_set_ignore is rated Medium
This tool creates or modifies data (vulnerability status/acknowledgment records) in a reversible manner. It does not delete data, execute external code, move money, or perform irreversible destruction. The operation can be undone by un-ignoring the CVE.
From the tool's definition Tool name 'cve_set_ignore' and description 'Ignore/dismiss a CVE vulnerability finding' indicate the tool modifies the state of vulnerability records by marking them as ignored or dismissed.
Attacks that exploit this kind of access
The rule that runs cve_set_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_ignore, this is the rule to start with:
cve_set_ignore stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Aapanel, apply this rule, and every cve_set_ignore call is checked against it from then on.
Questions about cve_set_ignore
Ignore/dismiss a CVE vulnerability finding. It is categorised as a Write tool in the Aapanel MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Aapanel MCP server in PolicyLayer and add a rule for cve_set_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_ignore is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the cve_set_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_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_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.
This server
Across the catalogue