Skip to main content
Glama
intruder-io

intruder-mcp

Official

list_licenses

View your Intruder account's license usage and limits, including infrastructure and application licenses. Each used license is tied to a target for 30 days.

Instructions

List license information for the Intruder account. Shows usage and limits for infrastructure and application licenses. When a license is used, it is tied to the target that used it for 30 days.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The MCP tool handler that lists license information. Calls api.list_licenses_all() and formats the results showing infrastructure and application license totals, available, and consumed counts.
    @mcp.tool()
    async def list_licenses() -> str:
        """
        List license information for the Intruder account. Shows usage and limits for infrastructure and application licenses. When a license is used, it is tied to the target that used it for 30 days.
        """
        licenses = api.list_licenses_all()
        formatted = []
        for license in licenses:
            formatted.append("Infrastructure Licenses:")
            formatted.append(f"  Total: {license.total_infrastructure_licenses}")
            formatted.append(f"  Available: {license.available_infrastructure_licenses}")
            formatted.append(f"  Consumed: {license.consumed_infrastructure_licenses}")
            formatted.append("")
            formatted.append("Application Licenses:")
            formatted.append(f"  Total: {license.total_application_licenses}")
            formatted.append(f"  Available: {license.available_application_licenses}")
            formatted.append(f"  Consumed: {license.consumed_application_licenses}")
            formatted.append("")
        return "\n".join(formatted)
  • API client method that calls the GET /licenses/ endpoint with optional pagination params.
    def list_licenses(self, limit: Optional[int] = None, offset: Optional[int] = None) -> PaginatedLicensesList:
        params = {}
        if limit:
            params["limit"] = limit
        if offset:
            params["offset"] = offset
        return PaginatedLicensesList(**self.client.get(f"{self.base_url}/licenses/", params=params).json())
  • Helper that paginates through all licenses using list_licenses with offset/limit.
    def list_licenses_all(self) -> Generator[Licenses, None, None]:
        offset = 0
        while True:
            response = self.list_licenses(limit=100, offset=offset)
            for license in response.results:
                yield license
            if not response.next:
                break
            offset += len(response.results)
  • Pydantic model defining the Licenses schema with infrastructure and application license fields.
    class Licenses(BaseModel):
        total_infrastructure_licenses: int
        available_infrastructure_licenses: int
        consumed_infrastructure_licenses: int
        total_application_licenses: int
        available_application_licenses: int
        consumed_application_licenses: int
  • Pagination wrapper for Licenses list, extending PaginatedResponse.
    class PaginatedLicensesList(PaginatedResponse):
        results: List[Licenses]
Behavior4/5

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

Adds crucial insight that when a license is used it is tied to the target for 30 days. No annotations provided, so description carries burden; it covers important behavioral detail.

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?

Two concise sentences, no fluff, first sentence states purpose, second adds behavioral context.

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?

Given no parameters and presence of output schema, the description adequately explains what is shown (usage and limits) and adds behavioral detail. Could mention return format but sufficient.

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, so the description does not need to add param info. Baseline 4 for 0 parameters with 100% schema coverage.

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?

Clearly states it lists license information for the Intruder account, showing usage and limits. This is a specific verb+resource combination with no similar sibling tool.

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?

The description implies use when checking license usage, but doesn't explicitly state when not to use or alternative tools. However, with no parameters and distinct purpose, it is still clear.

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