Low Risk

list_network_shares_ignoring_sysvol

List network share(s), ignoring SYSVOL

How to control list_network_shares_ignoring_sysvol ↓

AI agents call list_network_shares_ignoring_sysvol 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

This tool retrieves information about network shares from an Active Directory environment. It is fundamentally a Read operation (query, list, fetch). However, the severity is elevated to medium rather than low because: (1) the BloodHound context suggests this is part of a security reconnaissance toolkit that identifies attack paths and privilege escalation routes; (2) network share enumeration is often a precursor…

From the tool's definition Tool name contains 'list' and description states 'List network share(s)' — this is a query/retrieval operation with no modification, deletion, or execution.

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

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

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

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

Go deeper

What does the list_network_shares_ignoring_sysvol tool do? +

List network share(s), ignoring SYSVOL. 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 list_network_shares_ignoring_sysvol? +

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

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

Can I rate-limit list_network_shares_ignoring_sysvol? +

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

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

list_network_shares_ignoring_sysvol is provided by the BloodHound MCP server (stevenyu113228/bloodhound-mcp). 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.

Deterministic rules across all 106 BloodHound MCP tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

106 BloodHound MCP tools catalogued and risk-classified — across an index of 42,500+ 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.