Re-enable a previously disabled Active Directory user account through Microsoft Defender for Identity. Use after threat has been remediated.
AI agents use enable_ad_account to create or update resources in Response MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Response MCP Server environment.
This tool modifies AD account state (disabled → enabled), restoring user access. While reversible (can be disabled again), it is a material change to security posture and authentication infrastructure. It does not delete data (Destructive), move money (Financial), or execute arbitrary code (Execute), but it does alter identity systems in a way that could grant unauthorized access if misused by an agent.
From the tool's definition Tool description states it 're-enable[s] a previously disabled Active Directory user account' — a direct modification of identity infrastructure that creates or restores account access rights.
Documented attack patterns abuse exactly the kind of access enable_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 enable_ad_account:
{
"version": "1",
"default": "deny",
"tools": {
"enable_ad_account": {
"limits": [
{
"counter": "enable_ad_account_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}enable_ad_account stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Re-enable a previously disabled Active Directory user account through Microsoft Defender for Identity. Use after threat has been remediated. It is categorised as a Write tool in the Response MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Response MCP Server MCP server in PolicyLayer and add a rule for enable_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.
enable_ad_account is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the enable_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 enable_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.
enable_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.