Skip to main content
Glama
intruder-io

intruder-mcp

Official
by intruder-io
OverviewSchemaRelated ServersScoreDiscussions
Python
Hybrid

cancel_scan

Stop an active security scan in Intruder.IO by providing the scan ID to terminate ongoing vulnerability assessments.

Instructions

    Cancel a running scan.

    Args:
        scan_id: The ID of the scan to cancel

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
scan_idYes

Implementation Reference

  • intruder_mcp/server.py:182-191 (handler)
    The handler function for the 'cancel_scan' tool, registered via @mcp.tool() decorator. It invokes the API client's cancel_scan method and formats the response.
    @mcp.tool()
async def cancel_scan(scan_id: int) -> str:
    """
    Cancel a running scan.

    Args:
        scan_id: The ID of the scan to cancel
    """
    result = api.cancel_scan(scan_id)
    return f"Cancelled scan {scan_id}: {result}"
  • intruder_mcp/api_client.py:188-189 (helper)
    Core implementation of cancel_scan in the IntruderAPI class. Performs the HTTP POST request to the Intruder API endpoint to cancel the specified scan.
    def cancel_scan(self, scan_id: int) -> str:
    return self.client.post(f"{self.base_url}/scans/{scan_id}/cancel/").text

Tool Definition Quality

C2.9/5.0
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states the action ('Cancel') but doesn't explain what cancellation entails (e.g., whether it's reversible, if data is preserved, or if it requires specific permissions). This is a significant gap for a mutation tool with zero annotation coverage.

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 is appropriately concise, using two sentences with no wasted words. The first sentence states the purpose clearly, and the second provides parameter details in a structured format, making it easy to parse.

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

Completeness2/5

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

Given the tool's complexity (a mutation operation), lack of annotations, no output schema, and incomplete parameter documentation (0% schema coverage), the description is insufficient. It doesn't cover behavioral aspects like side effects, error conditions, or return values, leaving critical gaps for an agent to use it correctly.

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

Parameters3/5

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

The description adds minimal parameter semantics by explaining that 'scan_id' is 'The ID of the scan to cancel', which provides basic context. However, with 0% schema description coverage and only one parameter, this is adequate but not comprehensive, aligning with the baseline expectation for such limited schema support.

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

Purpose4/5

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

The description clearly states the verb ('Cancel') and resource ('a running scan'), making the purpose immediately understandable. However, it doesn't explicitly distinguish this tool from potential alternatives like 'stop_scan' or 'abort_scan' (though none exist in the sibling list), which prevents a perfect score.

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

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool versus alternatives, prerequisites (e.g., the scan must be running), or what happens after cancellation. It mentions 'a running scan' but doesn't clarify if this applies to pending or completed scans, leaving usage context vague.

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