intruder-mcp

Official

Overview Schema Source Related Servers Discussions Admin

snooze_occurrence

Snooze a specific issue occurrence to pause alerts, using a reason like false positive or accepted risk and an optional duration.

Instructions

    Snooze a specific occurrence of an issue.

    To snooze a whole issue, list its occurrences with list_occurrences and snooze each one.

    Args:
        issue_id: The ID of the issue
        occurrence_id: The ID of the occurrence to snooze
        reason: Reason for snoozing (required, must be one of ACCEPT_RISK, FALSE_POSITIVE, MITIGATING_CONTROLS)
        details: Optional free-text details for the snooze
        duration: Optional number of duration_type units to snooze for (ignored when duration_type is 'forever')
        duration_type: Optional duration type, one of 'forever', 'day', 'week', 'month'

    The reasons mean:
        - ACCEPT_RISK - Risk accepted for this specific occurrence
        - FALSE_POSITIVE - False positive - occurrence has been verified as not exploitable
        - MITIGATING_CONTROLS - Mitigating controls are in place for this occurrence

Input Schema

TableJSON Schema

Name	Required	Description	Default
`reason`	Yes
`details`	No
`duration`	No
`issue_id`	Yes
`duration_type`	No
`occurrence_id`	Yes

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv0.1.2May 3, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "result": {
+      "title": "Result",
+      "type": "string"
+    }
+  },
+  "required": [
+    "result"
+  ],
+  "title": "snooze_occurrenceOutput",
+  "type": "object"
+}

First observedAug 15, 2025

TDQS

A4.4/5.0

Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description carries the full burden and does substantial work: it discloses the required reason enumeration and the meaning of each reason value, plus the interaction that duration is ignored when duration_type is 'forever'. It omits permissions, reversibility (e.g., how to un-snooze), and side effects, which keeps it below 5.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loads the purpose, then the usage alternative, then args and reason glosses. Slightly redundant — the reason enum is listed in the Args block and then re-explained in a separate section — but every part is informative and structured.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 6-param mutation tool with an output schema (so returns need not be explained), the description covers all arguments and the workflow alternative. It stops short of covering permissions or how to reverse a snooze, which an agent might need for a state-changing operation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must compensate, and it does: all six parameters are documented, including the reason enum values (ACCEPT_RISK, FALSE_POSITIVE, MITIGATING_CONTROLS) with their meanings, and the duration/duration_type relationship.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb (snooze) and resource (a specific occurrence of an issue), and contrasts it with the whole-issue case handled by list_occurrences. An agent can distinguish it from siblings without opening the schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly tells the agent how to handle the alternative case — to snooze a whole issue, list occurrences with list_occurrences and snooze each. It gives clear context but no explicit when-not-to-use or exclusion conditions.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.