Skip to main content
Glama
mwnickerson

BloodHound MCP Server

by mwnickerson

get_user_sql_admin_rights

Retrieve SQL administrative rights for a user to identify potential lateral movement and privilege escalation paths in Active Directory security assessments.

Instructions

Retrieves the SQL administrative rights of a specific user within the domain.
SQL administrative rights allow a user to perform administrative tasks on a SQL Server.
These rights can be abused for lateral movement and privilege escalation within the domain.

Args:
    user_id: The ID of the user to query
    limit: Maximum number of SQL administrative rights to return (default: 100)
    skip: Number of SQL 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 describes the action ('retrieves') and adds security context about potential abuse, which is useful. However, it lacks details on permissions needed, rate limits, pagination behavior beyond skip/limit, or response format, leaving gaps in operational transparency.

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 and front-loaded with the core purpose, followed by parameter explanations. Sentences are efficient, with no wasted words. It could be slightly more concise by integrating the security note into the main purpose, but overall it's appropriately sized and clear.

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?

Given 3 parameters, 0% schema coverage, no annotations, and no output schema, the description provides adequate basics but lacks depth. It covers purpose and parameters well but misses behavioral details like error handling, authentication needs, or example outputs. For a tool with moderate complexity and no structured support, it's minimally complete but could be more comprehensive.

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?

Schema description coverage is 0%, so the description must compensate. It provides clear semantics for all three parameters: user_id specifies the target, limit controls result count with a default, and skip handles pagination. This adds meaningful context beyond the bare schema, though it could detail data types or constraints more explicitly.

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 ('SQL administrative rights of a specific user within the domain'), making the purpose specific and actionable. It distinguishes from siblings by focusing on SQL admin rights for users, unlike tools like get_computer_sql_admin_rights or get_user_admin_rights, which target different resources or rights types.

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 'a specific user within the domain' and the security context of SQL rights, but it does not explicitly state when to use this tool versus alternatives like get_computer_sql_admin_rights or general user rights tools. No exclusions or prerequisites are provided, leaving usage context partially inferred.

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