start_task · Greenbone MCP: Risk & Policy

WHAT IT DOES

What start_task does on GreenboneMCP

AI agents invoke start_task to trigger actions in GreenboneMCP. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.

WHY IT NEEDS A POLICY

Why start_task needs a policy

This tool initiates an external operation (vulnerability scan execution) whose effects depend on the task configuration and target systems. While scanning itself is legitimate, an AI agent misusing this could launch unintended scans against arbitrary targets, consume resources, trigger alerts on monitored systems, or generate noise.

From the tool's definition Tool name 'start_task' and description 'Start a scan task with a given task ID' indicates the tool triggers execution of a vulnerability scanning operation.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

start_task Rate-limited

start_task stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "start_task": {
      "limits": [
        {
          "counter": "start_task_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches GreenboneMCP, so you can run agents against it safely.

FAQ

Questions about start_task

What does the start_task tool do? +

Start a scan task with a given task ID. It is categorised as a Execute tool in the GreenboneMCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on start_task? +

Register the Greenbone MCP server in PolicyLayer and add a rule for start_task: 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 start_task? +

start_task is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit start_task? +

Yes. Add a rate_limit block to the start_task 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 start_task completely? +

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

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