Skip to main content
Glama
mwnickerson

BloodHound MCP Server

by mwnickerson

get_group_ps_remote_rights

Query remote PowerShell execution rights for a specific Active Directory group to identify potential lateral movement and privilege escalation paths in BloodHound security analysis.

Instructions

Retrieves the remote PowerShell rights of a specific group within the domain.
Remote PowerShell rights allow a group to execute PowerShell commands on a remote computer.
These rights can be abused for lateral movement and privilege escalation within the domain.

Args:
    group_id: The ID of the group to query
    limit: Maximum number of remote PowerShell rights to return (default: 100)
    skip: Number of remote PowerShell rights to skip for pagination (default: 0)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
group_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 full burden. It explains the security implications ('can be abused for lateral movement and privilege escalation'), which adds useful behavioral context beyond just being a read operation. However, it doesn't mention permissions required, rate limits, error conditions, or what the return format looks like, leaving gaps in behavioral understanding.

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 appropriately sized with three purpose-focused sentences followed by a well-structured Args section. The security context sentence earns its place by providing important behavioral insight. Minor improvement could be front-loading the Args section more clearly.

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 read-only tool with 3 parameters and no output schema, the description does reasonably well on purpose and parameters. However, without annotations and with no output schema, it should ideally describe the return format or structure. The security context helps, but completeness is limited by missing output information.

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?

With 0% schema description coverage, the description fully compensates by providing clear documentation for all 3 parameters in the Args section. It explains group_id's purpose, defines limit with default value and meaning, and explains skip for pagination with default. This adds significant 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 ('remote PowerShell rights of a specific group within the domain'), making the purpose explicit. It distinguishes from siblings by focusing on group-level PowerShell rights (vs. computer-level or user-level rights tools like get_computer_ps_remote_rights or get_user_ps_remote_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 context by explaining what remote PowerShell rights are and their security implications, but doesn't explicitly state when to use this tool versus alternatives. No specific exclusions or prerequisites are mentioned, leaving the agent to infer from the tool name and description alone.

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