Skip to main content
Glama
intruder-io

intruder-mcp

Official

list_targets

Retrieve all targets in your Intruder account with their IDs and status. Identify target statuses like live or unscanned.

Instructions

    List all targets in the Intruder account and their associated IDs and status (one of 'live', 'license_exceeded', 'unscanned', 'unresponsive', 'agent_uninstalled').
    

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The MCP tool handler for 'list_targets'. It calls api.list_targets_all() and formats the output as a string of IDs, addresses, and statuses.
    async def list_targets() -> str:
        """
        List all targets in the Intruder account and their associated IDs and status (one of 'live', 'license_exceeded', 'unscanned', 'unresponsive', 'agent_uninstalled').
        """
    
        targets = api.list_targets_all()
        formatted = [f"{target.id} - {target.address} ({target.target_status})" for target in targets]
        return "\n".join(formatted)
  • Registration of the 'list_targets' tool via the @mcp.tool() decorator on the async function.
    @mcp.tool()
    async def list_targets() -> str:
  • Helper method list_targets_all() that paginates through all targets via the API, yielding Target objects.
    def list_targets_all(self, address: Optional[str] = None, target_status: Optional[str] = None) -> Generator[Target, None, None]:
        offset = 0
        while True:
            response = self.list_targets(address=address, target_status=target_status,
                                       limit=100, offset=offset)
            for target in response.results:
                yield target
            if not response.next:
                break
            offset += len(response.results)
  • Helper method list_targets() that calls the /targets/ API endpoint with optional filters and returns a PaginatedTargetList.
    def list_targets(self, address: Optional[str] = None, target_status: Optional[str] = None,
                    limit: Optional[int] = None, offset: Optional[int] = None) -> PaginatedTargetList:
        params = {}
        if address:
            params["address"] = address
        if target_status:
            params["target_status"] = target_status
        if limit:
            params["limit"] = limit
        if offset:
            params["offset"] = offset
        return PaginatedTargetList(**self.client.get(f"{self.base_url}/targets/", params=params).json())
  • The Target Pydantic model used for deserializing target data returned by the API, including id, address, target_status, tags, etc.
    class Target(BaseModel):
        id: int
        address: str
        has_api_schemas: bool
        has_authentications: bool
        license_type: Optional[LicenseTypeEnum] = None
        tags: Optional[List[Optional[str]]] = None
        target_status: TargetStatusEnum
Behavior2/5

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

No annotations provided. The description only states what the tool lists but does not disclose any behavioral traits such as read-only nature, rate limits, or pagination. Minimal value beyond the tool name.

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

Conciseness5/5

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

Single sentence that is front-loaded with the action and object. No wasted words; every part contributes to understanding.

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?

For a parameterless tool with an output schema, the description is adequate but lacks mention of ordering, filtering, or pagination. Complete for a basic list-all but could be more helpful.

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?

No parameters exist, and schema description coverage is 100% vacuously. Baseline of 4 is appropriate since there is nothing to add.

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 clearly states the verb 'List', the resource 'all targets in the Intruder account', and the specific output including IDs and status with enumerated values. It implicitly distinguishes from sibling tools like create_targets and delete_target.

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 on when to use this tool versus alternatives like list_scans or list_issues. Does not mention when not to use it or any prerequisites.

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