Skip to main content
Glama
intruder-io

intruder-mcp

Official

create_scan

Initiate security scans on target addresses or tagged assets to identify vulnerabilities and assess network security posture.

Instructions

    Create a new scan.

    Args:
        target_addresses: List of target addresses to scan
        tag_names: List of tag names to scan targets with these tags
    

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
target_addressesNo
tag_namesNo

Implementation Reference

  • The FastMCP tool handler for 'create_scan', which invokes the IntruderAPI to create a scan and returns a confirmation message with the scan ID and type.
    @mcp.tool()
    async def create_scan(target_addresses: Optional[List[str]] = None, tag_names: Optional[List[str]] = None) -> str:
        """
        Create a new scan.
    
        Args:
            target_addresses: List of target addresses to scan
            tag_names: List of tag names to scan targets with these tags
        """
        scan = api.create_scan(target_addresses=target_addresses, tag_names=tag_names)
        return f"Created scan {scan.id} ({scan.scan_type})"
  • Pydantic model defining the input schema (ScanRequest) for the create_scan API request, used in the helper to validate and serialize parameters.
    class ScanRequest(BaseModel):
        target_addresses: Optional[List[str]] = None
        tag_names: Optional[List[str]] = Field(None, min_items=1)
  • The IntruderAPI.create_scan helper method that uses ScanRequest to POST to the Intruder API's /scans/ endpoint to create the scan.
    def create_scan(self, target_addresses: Optional[List[str]] = None,
                   tag_names: Optional[List[str]] = None) -> Scan:
        data = ScanRequest(target_addresses=target_addresses, tag_names=tag_names)
        return Scan(**self.client.post(f"{self.base_url}/scans/", json=data.dict(exclude_none=True)).json())
Behavior2/5

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

With no annotations provided, the description carries full burden but offers minimal behavioral context. It states this creates something but doesn't describe what happens after creation, whether this triggers an immediate scan, what permissions are needed, or what the expected response looks like. For a creation tool with zero annotation coverage, this is insufficient.

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 efficiently structured with a brief purpose statement followed by parameter documentation. Every sentence serves a purpose, though the formatting with extra whitespace could be slightly cleaner.

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?

For a creation tool with no annotations and no output schema, the description is incomplete. It doesn't explain what a 'scan' is, what happens after creation, what the tool returns, or how it relates to other tools in the system. The parameter documentation is good, but overall context is lacking.

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?

The description provides clear parameter documentation in the Args section, explaining what 'target_addresses' and 'tag_names' represent. With 0% schema description coverage, this fully compensates by adding meaningful semantics beyond the schema's basic structure and titles.

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

Purpose3/5

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

The description states 'Create a new scan' which is a clear verb+resource combination, but it's somewhat vague about what a 'scan' entails in this context. It doesn't differentiate from sibling tools like 'get_scan' or 'list_scans' beyond the obvious creation vs retrieval distinction.

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?

No guidance is provided about when to use this tool versus alternatives. The description doesn't mention prerequisites, when scanning is appropriate, or how this relates to sibling tools like 'create_targets' or 'create_target_tag' which might be needed first.

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