fetch_latest_report

Retrieve the most recent report for a scan task, optionally including full results.

Server GreenboneMCP matteocolazilli/greenbonemcp
Category Read
Risk class Low
Parameters 00 required

What fetch_latest_report does on GreenboneMCP

AI agents call fetch_latest_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.

Why fetch_latest_report needs a policy

This tool queries and returns existing vulnerability scan reports. It has no side effects, does not modify state, and does not trigger scans or external operations—it only fetches pre-computed results. The sibling tools like start_scan, stop_task, and restart_scan perform write/execute operations; fetch_latest_report is strictly informational. Classification as Read is appropriate for a reporting/query operation.

From the tool's definition Tool description states 'Retrieve the most recent report' with no mention of creating, modifying, deleting, or executing operations. The verb 'retrieve' and context of 'report' indicate a passive data retrieval operation.

Questions about fetch_latest_report

What does the fetch_latest_report tool do? +

Retrieve the most recent report for a scan task, optionally including full results. It is categorised as a Read tool in the GreenboneMCP MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on fetch_latest_report? +

Register the Greenbone MCP server in PolicyLayer and add a rule for fetch_latest_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.

What risk level is fetch_latest_report? +

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

Can I rate-limit fetch_latest_report? +

Yes. Add a rate_limit block to the fetch_latest_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.

How do I block fetch_latest_report completely? +

Set action: deny in the PolicyLayer policy for fetch_latest_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.

What MCP server provides fetch_latest_report? +

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

// LOOK UP ANOTHER 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 →

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.