delta_report
AI agents call delta_report to retrieve information from GreenboneMCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Delta reports compare vulnerability scan results between two points in time to identify changes. This is fundamentally a data retrieval and analysis operation with no side effects on systems or data. While the description is uninformative, the name and server context strongly indicate this generates or fetches comparative reports rather than modifying or executing operations.
From the tool's definition Tool name 'delta_report' and context of sibling tools (fetch_latest_report, scan_status) suggest report retrieval. Description is empty, limiting direct evidence. Delta comparisons are mentioned in server description as a report retrieval workflow.
Attacks that exploit this kind of access
delta_report. It is categorised as a Read tool in the GreenboneMCP MCP Server, which means it retrieves data without modifying state.
Register the Greenbone MCP server in PolicyLayer and add a rule for delta_report: 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 GreenboneMCP. Nothing to install.
delta_report 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 delta_report 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 delta_report. 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.
delta_report is provided by the Greenbone MCP server (matteocolazilli/greenbonemcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →