Disable an Active Directory user account through Microsoft Defender for Identity. Use when credentials are compromised or account shows malicious activity. The account will be unable to authenticate.
AI agents call disable_ad_account to permanently remove resources in Response MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Disabling an AD account prevents the user from authenticating anywhere in the domain. This is a high-impact, potentially irreversible action (without a corresponding re-enable action visible in the toolset) that locks out access to all systems. It constitutes a destructive action against an identity resource with broad blast radius if misused on a legitimate account.
From the tool's definition Disable an Active Directory user account... The account will be unable to authenticate.
Documented attack patterns abuse exactly the kind of access disable_ad_account gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Response MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for disable_ad_account:
{
"version": "1",
"default": "deny",
"hide": [
"disable_ad_account"
]
} disable_ad_account disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.
Free to start. No card required.
Disable an Active Directory user account through Microsoft Defender for Identity. Use when credentials are compromised or account shows malicious activity. The account will be unable to authenticate. It is categorised as a Destructive tool in the Response MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Response MCP Server MCP server in PolicyLayer and add a rule for disable_ad_account: 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 Response MCP Server. Nothing to install.
disable_ad_account is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the disable_ad_account 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 disable_ad_account. 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.
disable_ad_account is provided by the Response MCP Server MCP server (markolauren/responsemcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Response MCP Server, 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.
23 Response MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.