update_finding_status

THE RISK

Medium Risk

Why update_finding_status needs a policy

This tool creates or modifies data reversibly by changing finding status within a vulnerability management system. Status updates can be reverted or corrected later, so it does not meet the Destructive threshold (no data deletion/purging).

From the tool's definition Tool description explicitly states 'Update the status of a finding' with enumerated status values (Active, Verified, False Positive, Mitigated, Inactive). This modifies the state of vulnerability records in DefectDojo.

Documented attack patterns abuse exactly the kind of access update_finding_status gives an agent:

POLICY

How to control update_finding_status

PolicyLayer is an MCP gateway — it sits between your AI agents and DefectDojo MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for update_finding_status:

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "update_finding_status": {
      "limits": [
        {
          "counter": "update_finding_status_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

update_finding_status stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

Create a free account and register DefectDojo MCP Server — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

LIMIT THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More DefectDojo MCP Server tools

Write add_finding_note Add a note to a finding Write close_engagement Close an engagement Write create_engagement Create a new engagement Write create_finding Create a new finding Write update_engagement Update an existing engagement Read get_engagement Get a specific engagement by ID Read get_findings Get findings with filtering options and pagination support Read list_engagements List engagements with optional filtering and pagination support

All 11 DefectDojo MCP Server tools →

Write tools on other servers

M-Team MCP Server download_torrent YouTube MCP Server generate_video_title Android Forensics ADB MCP Server combine_reports 0xarchive web3_signup

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Argument validation → Checking tool call arguments against schema and policy before they run.
Scoped token → Per-person credentials that grant a defined subset of servers and tools.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about update_finding_status

What does the update_finding_status tool do? +

Update the status of a finding (Active, Verified, False Positive, Mitigated, Inactive). It is categorised as a Write tool in the DefectDojo MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on update_finding_status? +

Register the DefectDojo MCP Server MCP server in PolicyLayer and add a rule for update_finding_status: 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 DefectDojo MCP Server. Nothing to install.

What risk level is update_finding_status? +

update_finding_status is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit update_finding_status? +

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

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

update_finding_status is provided by the DefectDojo MCP Server MCP server (jamiesonio/defectdojo-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every DefectDojo MCP Server tool call.

Start from DefectDojo MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →