cve_get_tmp_result
Get temporary/intermediate CVE scan results.
This record as markdown: /tools/aapanel-mcp/cve-get-tmp-result.md
What cve_get_tmp_result does on Aapanel
AI agents call cve_get_tmp_result to retrieve information from Aapanel without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why cve_get_tmp_result is rated Low
This tool reads and retrieves existing CVE scan results. It performs no writes, deletions, executions, or financial operations. The 'get' verb and retrieval-focused description confirm it is a read-only query operation with minimal blast radius even if misused by an agent.
From the tool's definition Tool name contains 'get' and description states 'Get temporary/intermediate CVE scan results' — retrieves scan data without modification or side effects.
Attacks that exploit this kind of access
The rule that runs cve_get_tmp_result 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_get_tmp_result, this is the rule to start with:
cve_get_tmp_result is read-only, so it stays allowed. 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_get_tmp_result call is checked against it from then on.
Questions about cve_get_tmp_result
Get temporary/intermediate CVE scan results. It is categorised as a Read tool in the Aapanel MCP Server, which means it retrieves data without modifying state.
Register the Aapanel MCP server in PolicyLayer and add a rule for cve_get_tmp_result: 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_get_tmp_result is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the cve_get_tmp_result 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_get_tmp_result. 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_get_tmp_result 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