Skip to main content
Glama
mwnickerson

BloodHound MCP Server

by mwnickerson

get_user_admin_rights

Query a user's administrative privileges in Active Directory to identify potential security risks like lateral movement, persistence, or privilege escalation.

Instructions

Retrieves the administrative rights of a specific user in the domain.
Administrative rights are privileges that allow a user 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:
    user_id: The ID of the user 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
user_idYes
limitNo
skipNo
Behavior3/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It clearly indicates this is a read operation ('Retrieves'), mentions the security context (Active Directory administrative rights), and warns about potential abuse implications. However, it doesn't disclose important behavioral aspects like authentication requirements, rate limits, error conditions, or what happens when the user doesn't exist.

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 well-structured with a clear purpose statement followed by explanatory context and parameter documentation. Every sentence adds value: the first states the core function, the second explains what administrative rights are, the third provides security context, and the parameter section adds necessary details. It could be slightly more concise by integrating the security context more tightly.

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 tool with 3 parameters, 0% schema description coverage, no annotations, and no output schema, the description does reasonably well. It covers the purpose and parameters adequately but lacks information about return format, error handling, authentication requirements, and typical response structure. The security context about abuse is helpful but doesn't fully compensate for missing operational details.

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?

The description provides excellent parameter semantics beyond the input schema, which has 0% description coverage. It explains that 'user_id' identifies 'the user to query', clarifies that 'limit' controls 'maximum number of administrative rights to return' with a default, and specifies that 'skip' is for 'pagination' with a default. This fully compensates for the schema's lack of descriptions.

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 tool's purpose with a specific verb ('Retrieves') and resource ('administrative rights of a specific user in the domain'). It distinguishes from sibling tools like 'get_computer_admin_rights' by specifying user-focused rights rather than computer-focused, and from 'get_user_info' by focusing specifically on administrative privileges rather than general user information.

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?

The description provides no guidance on when to use this tool versus alternatives. While it mentions administrative rights can be abused for lateral movement, persistence, and privilege escalation, it doesn't specify when this tool should be chosen over other user-focused tools like 'get_user_info' or 'get_user_memberships', nor does it mention prerequisites or typical use cases.

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