Skip to main content
Glama
mwnickerson

BloodHound MCP Server

by mwnickerson

get_group_admin_rights

Retrieve administrative privileges for a specific Active Directory group to identify potential security risks like lateral movement and privilege escalation.

Instructions

Retrieves the administrative rights of a specific group in the domain.
Administrative rights are privileges that allow a group 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:
    group_id: The ID of the group 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
group_idYes
limitNo
skipNo
Behavior2/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 mentions that administrative rights 'can be abused' but doesn't clarify if this is a read-only operation, what permissions are required, whether it's rate-limited, or what the response format looks like. The description adds some security context but lacks operational details.

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 parameter documentation. Each sentence earns its place, though the security context about abuse could be more integrated. The front-loaded purpose statement is effective, and the Args section is organized.

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, no annotations, and no output schema, the description provides adequate parameter semantics but lacks behavioral context. It covers what the tool does and what parameters mean, but doesn't explain what the output looks like, error conditions, or operational constraints, leaving gaps for an AI agent.

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?

The schema description coverage is 0%, so the description must compensate. It provides clear explanations for all three parameters: 'group_id' identifies the target group, 'limit' controls maximum results with default, and 'skip' enables pagination with default. This adds substantial value 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 group'), making the purpose explicit. It distinguishes from sibling tools like 'get_group_info' or 'get_group_members' by focusing specifically on administrative rights rather than general group information or membership.

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 that administrative rights can be abused for lateral movement, persistence, and privilege escalation, it doesn't specify use cases, prerequisites, or comparisons to similar tools like 'get_user_admin_rights' or 'get_computer_admin_rights'.

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