sp_app_role_grant

THE RISK

Low Risk

Why sp_app_role_grant needs a policy

The tool name suggests granting application role permissions (possibly in a service principal or database context), which could be a Write or Execute action. However, the description is completely empty and the tool name is ambiguous in the context of a BloodHound/Active Directory analysis server. Without more information, classification is uncertain.

From the tool's definition Tool name 'sp_app_role_grant' and empty description provide no direct behavioral information

Documented attack patterns abuse exactly the kind of access sp_app_role_grant gives an agent:

POLICY

How to control sp_app_role_grant

PolicyLayer is an MCP gateway — it sits between your AI agents and BloodHound MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for sp_app_role_grant:

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "sp_app_role_grant": {
      "limits": [
        {
          "counter": "sp_app_role_grant_rate",
          "window": "minute",
          "max": 60,
          "scope": "grant"
        }
      ]
    }
  }
}

sp_app_role_grant gets a rate cap, and everything else on the server is denied unless you say otherwise.

Create a free account and register BloodHound MCP — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

SET A RULE FOR THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More BloodHound MCP tools

Execute query_bloodhound query_bloodhound Read find_all_domain_admins find_all_domain_admins Read find_all_kerberoastable_users find_all_kerberoastable_users Read find_asreproast_users find_asreproast_users Read find_ca_administrators find_ca_administrators Read find_certificate_enrollment_rights find_certificate_enrollment_rights Read find_computers_in_protected_users find_computers_in_protected_users Read find_computers_no_smb_signing find_computers_no_smb_signing

All 75 BloodHound MCP tools →

Other tools on other servers

Android Forensics ADB MCP Server generate_app_analysis_report Ethereum Tools add Math MCP Server complex_analysis_suite Crypto_MCP aes_encrypt

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Tool risk categories → How PolicyLayer classifies MCP tools by what they can do.
MCP tool → What an MCP tool is and how clients discover and call it.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about sp_app_role_grant

What does the sp_app_role_grant tool do? +

sp_app_role_grant. It is categorised as a Other tool in the BloodHound MCP MCP Server, which means it performs auxiliary operations.

How do I enforce a policy on sp_app_role_grant? +

Register the BloodHound MCP server in PolicyLayer and add a rule for sp_app_role_grant: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches BloodHound MCP. Nothing to install.

What risk level is sp_app_role_grant? +

sp_app_role_grant is a Other tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit sp_app_role_grant? +

Yes. Add a rate_limit block to the sp_app_role_grant rule in your PolicyLayer policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.

How do I block sp_app_role_grant completely? +

Set action: deny in the PolicyLayer policy for sp_app_role_grant. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.

What MCP server provides sp_app_role_grant? +

sp_app_role_grant is provided by the BloodHound MCP server (mordavid/bloodhound-mcp-ai). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every BloodHound MCP tool call.

Start from BloodHound MCP, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →