Skip to main content
Glama

port_leak_detector

Read-onlyIdempotent

[Non-invasive bounded TCP probe with SSRF protection. Read-only, side-effect free]. Probes target host for exposed critical infrastructure ports (MySQL 3306, Postgres 5432, Redis 6379, MongoDB 27017, Elasticsearch 9200, unauthenticated Docker 2375). Strictly non-destructive, with private IP / localhost SSRF protection. Usage: Use this tool to audit perimeter firewall configuration and identify exposed database ports. Does NOT exploit vulnerabilities or alter server configuration. Returns: JSON object with { target: string, scannedPortsCount: number, exposedPorts: Array<{ port: number, service: string, riskLevel: 'HIGH' | 'CRITICAL' }>, perimeterSecurityStatus: 'SECURE' | 'EXPOSED', recommendations: string[] }.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "hostname": "<hostname>"
    },
    "name": "port_leak_detector"
  }
}

Input Schema

NameRequiredDescriptionDefault
hostnameYesTarget domain or public IP address to inspect
timeoutMsNoPer-port socket connect timeout in milliseconds (500-3000ms)
customPortsNoOptional list of specific custom ports to probe (max 10)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Annotations only cover readOnly/idempotent, but the description adds substantive behavior: private-IP and localhost SSRF blocking, strict non-destructiveness, bounded connect timeouts, and the exact JSON return shape including risk levels and perimeter status. That is real context an agent cannot get from the annotations or schema.

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?

Front-loads the bracketed safety summary, then a Usage line and a Returns line, so an agent can skim in order. The bracketed preamble is slightly redundant with the later 'Strictly non-destructive' sentence, costing a bit of tightness.

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

Completeness5/5

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

No output schema exists, yet the description spells out the return object fields, the security posture values, and the SSRF guardrails. For a read-only probe with three fully documented params, nothing an agent needs before calling is missing.

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?

Schema description coverage is 100%, so hostname, timeoutMs, and customPorts are already documented with defaults and ranges. The description adds no per-parameter syntax or constraints beyond restating that it probes a target host, so baseline 3 applies.

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?

States a specific verb and resource ('bounded TCP probe' against a target host) and enumerates exactly which ports are checked (MySQL 3306, Postgres 5432, Redis 6379, MongoDB 27017, Elasticsearch 9200, Docker 2375). That port inventory makes it unmistakable versus the sibling RDAP, email, and TLS/HTTP tools without needing to name them.

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?

Explicitly frames the use case ('audit perimeter firewall configuration and identify exposed database ports') and states a negative boundary ('Does NOT exploit vulnerabilities or alter server configuration'). No alternative tool is named for overlapping needs, so it stops short of a 5.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources