AI agents call get_dc_features to retrieve information from LegacyMCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries Active Directory Domain Controller feature information, which is a read-only data retrieval operation. It has no side effects and follows the pattern of other 'get_' prefixed tools on the server. The medium severity reflects that DC feature enumeration could inform reconnaissance attacks or lateral movement strategies, but causes no direct damage.
From the tool's definition Tool name 'get_dc_features' indicates retrieval of Domain Controller features; consistent with sibling tools that are all Read operations (get_blocked_inheritance_ous, get_certification_authorities, get_computer_summary, get_computers, get_dc_file_locations,…
Attacks that exploit this kind of access
get_dc_features. It is categorised as a Read tool in the LegacyMCP MCP Server, which means it retrieves data without modifying state.
Register the Legacy MCP server in PolicyLayer and add a rule for get_dc_features: 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 LegacyMCP. Nothing to install.
get_dc_features is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_dc_features 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.
Set action: deny in the PolicyLayer policy for get_dc_features. 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.
get_dc_features is provided by the Legacy MCP server (marco-lelli/legacy-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →