Low Risk

templates_no_security_ext

templates_no_security_ext

How to control templates_no_security_ext ↓

What templates_no_security_ext does on BloodHound MCP

AI agents call templates_no_security_ext 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_no_security_ext needs a policy

This tool operates within BloodHound's threat analysis framework, which identifies security weaknesses in Active Directory. The naming pattern matches sibling reconnaissance tools that retrieve data about vulnerable configurations, permissions, and attack paths. No evidence of modification, deletion, or execution of external operations.

From the tool's definition Tool name 'templates_no_security_ext' suggests querying templates lacking security extensions, consistent with BloodHound's attack path analysis pattern.

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

How to control templates_no_security_ext

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

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

templates_no_security_ext 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_no_security_ext

What does the templates_no_security_ext tool do? +

templates_no_security_ext. 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_no_security_ext? +

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

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

Can I rate-limit templates_no_security_ext? +

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

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

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