Low Risk

templates_with_user_san

templates_with_user_san

How to control templates_with_user_san ↓

What templates_with_user_san does on BloodHound MCP

AI agents call templates_with_user_san to retrieve information from BloodHound MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

Why templates_with_user_san needs a policy

This tool queries BloodHound's database to identify certificate templates with user SAN vulnerability—a read-only reconnaissance operation. No side effects, data modification, or external execution occurs. The description is empty, reducing confidence slightly, but the naming convention and server context strongly indicate it retrieves security configuration data for analysis.

From the tool's definition Tool name 'templates_with_user_san' suggests querying BloodHound for certificate templates allowing user Subject Alternative Names.

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

How to control templates_with_user_san

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 templates_with_user_san:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "templates_with_user_san": {}
  }
}

templates_with_user_san is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

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

Free to start. No card required.

Related tools and policies

Go deeper

Questions about templates_with_user_san

What does the templates_with_user_san tool do? +

templates_with_user_san. It is categorised as a Read tool in the BloodHound MCP MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on templates_with_user_san? +

Register the BloodHound MCP server in PolicyLayer and add a rule for templates_with_user_san: 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 templates_with_user_san? +

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

Can I rate-limit templates_with_user_san? +

Yes. Add a rate_limit block to the templates_with_user_san 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 templates_with_user_san completely? +

Set action: deny in the PolicyLayer policy for templates_with_user_san. 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 templates_with_user_san? +

templates_with_user_san 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.

Free to start. No card required.

75 BloodHound MCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.