Skip to main content
Glama

rdp_audit

Audit a target's RDP service to check its encryption level and extract exposed NTLM identity information. Use it to assess remote desktop security posture and authentication details.

Instructions

Check RDP encryption level and NTLM identity info exposed by a target.

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": {
      "target": "<target>"
    },
    "name": "rdp_audit"
  }
}

Input Schema

NameRequiredDescriptionDefault
targetYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.8/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It implies reconnaissance by saying it checks exposed information, but it does not state whether the probe is read-only, intrusive, authenticated, rate-limited, or dangerous to production systems.

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 one sentence, front-loaded with the action and resource, and contains no filler. Its brevity is appropriate, though it borders on under-specification rather than maximal conciseness.

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?

An output schema exists, so return values need not be explained. For a simple one-parameter audit tool, the description states the core check but omits target format and behavioral safety details that an agent needs before invoking it against a live host.

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

Parameters2/5

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

Schema description coverage is 0% for the single target parameter, so the description would need to compensate. It only repeats that a target is involved and does not explain whether the target should be an IP address, hostname, or IP:port combination.

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 states a specific verb and resource: check RDP encryption level and NTLM identity information exposed by a target. It is clear what the tool does, though it does not explicitly distinguish itself from sibling protocol audit tools such as smb_audit or ssh_audit beyond naming RDP.

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?

There is no explicit when-to-use guidance, no exclusions, and no named alternatives. An agent can infer this is one of several protocol audits from the name, but the description itself leaves selection entirely to inference.

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