Retrieve a list of all configured scan targets.
AI agents call get_targets 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.
This tool retrieves and lists scan target configurations without creating, modifying, deleting, or executing anything. It is a simple data retrieval operation with no blast radius if misused by an AI agent, as it cannot change system state or compromise security directly. The low severity reflects that exposure of target lists is a lower-order risk compared to the ability to actually execute scans or delete data.
From the tool's definition Tool name 'get_targets' and description 'Retrieve a list of all configured scan targets' indicate a read-only operation that queries existing data without modification or side effects.
Attacks that exploit this kind of access
Retrieve a list of all configured scan targets. 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 get_targets: 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.
get_targets 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 get_targets 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 get_targets. 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.
get_targets 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 →