Skip to main content
Glama
mwnickerson

BloodHound MCP Server

by mwnickerson

get_computer_admin_rights

Query administrative rights for a specific computer to identify potential attack paths for lateral movement, persistence, or privilege escalation in Active Directory environments.

Instructions

Retrieves the administrative rights of a specific computer in the domain.
Administrative rights are privileges that allow a computer to perform administrative tasks on a Security Principal (user, group, or computer) in Active Directory.
These rights can be abused in a variety of ways include lateral movement, persistence, and privilege escalation.

Args:
    computer_id: The ID of the computer to query
    limit: Maximum number of administrative rights to return (default: 100)
    skip: Number of administrative rights to skip for pagination (default: 0)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
computer_idYes
limitNo
skipNo
Behavior4/5

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

With no annotations provided, the description carries full burden. It discloses that this is a read operation ('Retrieves'), includes pagination behavior via limit/skip parameters, and adds security context about how these rights can be abused. However, it doesn't mention authentication requirements, rate limits, or error conditions.

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?

Well-structured with purpose statement, domain context, security implications, and parameter documentation. The security abuse sentence could be considered slightly extraneous but provides valuable context. Overall efficient with clear sections.

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?

For a 3-parameter read tool with no annotations and no output schema, the description provides good coverage: clear purpose, parameter semantics, and behavioral context about pagination and security implications. Missing details about return format and exact output structure prevent a perfect score.

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

Parameters5/5

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

Schema description coverage is 0%, so the description must fully compensate. It provides clear documentation for all 3 parameters: computer_id (what to query), limit (maximum number to return with default), and skip (pagination offset with default). This adds essential meaning beyond the bare schema.

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 ('Retrieves') and resource ('administrative rights of a specific computer in the domain'), with additional context about what administrative rights are. It distinguishes from siblings like 'get_computer_info' or 'get_computer_memberships' by focusing specifically on admin rights.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage by mentioning the computer_id parameter and domain context, but does not explicitly state when to use this tool versus alternatives like 'get_computer_admin_users' or 'get_computer_controllers'. No exclusions or prerequisites are provided.

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/mwnickerson/bloodhound_mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server