Skip to main content
Glama
intruder-io

intruder-mcp

Official

snooze_occurrence

Snooze a specific occurrence of an issue by specifying issue ID, occurrence ID, and reason (ACCEPT_RISK, FALSE_POSITIVE, or MITIGATING_CONTROLS). Optionally set a duration and details.

Instructions

    Snooze a specific occurrence of an issue.

    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 details for the snooze
        duration: Optional duration for the snooze (in seconds)
        duration_type: Optional duration type (e.g., 'days', 'hours')
        
    The reasons mean:
        - ACCEPT_RISK - Risk accepted for the issue and all of its occurrences
        - FALSE_POSITIVE - False positive - issue and all occurrences have been verified as not exploitable
        - MITIGATING_CONTROLS - Mitigating controls are in place
    

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
issue_idYes
occurrence_idYes
reasonYes
detailsNo
durationNo
duration_typeNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • MCP tool handler function that snoozes a specific occurrence of an issue. Decorated with @mcp.tool() and named 'snooze_occurrence'. Accepts issue_id, occurrence_id, reason, details, duration, and duration_type. Delegates to api.snooze_occurrence() and returns the result message.
    @mcp.tool()
    async def snooze_occurrence(issue_id: int, occurrence_id: int, reason: str, details: Optional[str] = None, duration: Optional[int] = None, duration_type: Optional[str] = None) -> str:
        """
        Snooze a specific occurrence of an issue.
    
        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 details for the snooze
            duration: Optional duration for the snooze (in seconds)
            duration_type: Optional duration type (e.g., 'days', 'hours')
            
        The reasons mean:
            - ACCEPT_RISK - Risk accepted for the issue and all of its occurrences
            - FALSE_POSITIVE - False positive - issue and all occurrences have been verified as not exploitable
            - MITIGATING_CONTROLS - Mitigating controls are in place
        """
        result = api.snooze_occurrence(issue_id, occurrence_id, reason=reason, details=details, duration=duration, duration_type=duration_type)
        return result.get("message", str(result))
  • The tool is registered inline via the @mcp.tool() decorator on line 288 in server.py, where mcp is a FastMCP instance.
    @mcp.tool()
  • API client method that sends the POST request to snooze an occurrence. Constructs a SnoozeOccurrenceRequest and posts to /issues/{issue_id}/occurrences/{occurrence_id}/snooze/.
    def snooze_occurrence(self, issue_id: int, occurrence_id: int, reason: OccurrencesSnoozeReasonEnum, details: Optional[str] = None, duration: Optional[int] = None, duration_type: Optional[str] = None) -> dict:
        data = SnoozeOccurrenceRequest(details=details, duration=duration, duration_type=duration_type, reason=reason)
        return self.client.post(f"{self.base_url}/issues/{issue_id}/occurrences/{occurrence_id}/snooze/", json=data.dict(exclude_none=True)).json() 
  • Pydantic BaseModel schema for the snooze occurrence request payload. Contains optional details, duration, duration_type, and required reason field of type OccurrencesSnoozeReasonEnum.
    class SnoozeOccurrenceRequest(BaseModel):
        details: Optional[str] = None
        duration: Optional[int] = None
        duration_type: Optional[str] = None  # Should match DurationTypeEnum if defined
        reason: OccurrencesSnoozeReasonEnum 
  • Enum defining valid snooze reasons for occurrences: ACCEPT_RISK, FALSE_POSITIVE, MITIGATING_CONTROLS.
    class OccurrencesSnoozeReasonEnum(str, Enum):
        ACCEPT_RISK = "ACCEPT_RISK"
        FALSE_POSITIVE = "FALSE_POSITIVE"
        MITIGATING_CONTROLS = "MITIGATING_CONTROLS"
Behavior3/5

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

No annotations are provided, so the description fully bears the responsibility. It explains reasons in detail but does not disclose consequences like whether the occurrence is hidden or if it can be unsnoozed, leaving behavioral gaps.

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?

The description uses a clear docstring structure with Args and a reasons explanation block. It is informative but a bit lengthy; could be more concise while retaining clarity.

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

Completeness3/5

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

An output schema exists, so return values are presumably documented. However, the description lacks context on prerequisites, side effects, permissions, or reversibility, which are important for a mutation tool.

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

Parameters4/5

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

Schema coverage is 0%, so the description adds all meaning. It clarifies the reason enum values meaning, details, duration, and duration_type, which are not explained in the schema.

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?

The description explicitly states 'Snooze a specific occurrence of an issue,' which is a specific verb+resource combination. It clearly differentiates from sibling 'snooze_issue' by specifying occurrence-level vs issue-level.

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

Usage Guidelines3/5

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

No explicit guidance on when to use this tool versus alternatives like 'snooze_issue' or when not to use it. The context of 'occurrence' is clear but lacks comparative usage instructions.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/intruder-io/intruder-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server