deactivate_user

Deactivate (offboard) a user by setting active=false. Requires WRITE_ENABLED=true

SERVERServiceNow MCP Server SOURCE@aartiq/servicenow-mcp

Critical RISK CLASS

Category Destructive

Parameters 00 required

Recommended Hiddensee the rule below

Registry record Grade F, identity verified Pull the record →

This record as markdown: /tools/servicenow-mcp-server/deactivate-user.md

WHAT IT DOES

What deactivate_user does on ServiceNow MCP Server

AI agents call deactivate_user to permanently remove resources in ServiceNow MCP Server, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

RISK

Why deactivate_user is rated Critical

Deactivating a user account is a significant irreversible-in-effect action removing system access.

From the tool's definition Deactivate (offboard) a user by setting active=false

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs deactivate_user safely

PolicyLayer is an MCP gateway: it sits between your AI agents and ServiceNow MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For deactivate_user, this is the rule to start with:

deactivate_user Hidden

deactivate_user is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "hide": [
    "deactivate_user"
  ]
}

RESTRICT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect ServiceNow MCP Server, apply this rule, and every deactivate_user call is checked against it from then on.

FAQ

Questions about deactivate_user

What does the deactivate_user tool do? +

Deactivate (offboard) a user by setting active=false. Requires WRITE_ENABLED=true. It is categorised as a Destructive tool in the ServiceNow MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on deactivate_user? +

Register the ServiceNow MCP Server MCP server in PolicyLayer and add a rule for deactivate_user: 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 ServiceNow MCP Server. Nothing to install.

What risk level is deactivate_user? +

deactivate_user is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit deactivate_user? +

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

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

deactivate_user is provided by the ServiceNow MCP Server MCP server (@aartiq/servicenow-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on ServiceNow MCP Server, and thousands of servers like it.

This server

All 504 ServiceNow MCP Server tools → Critical-risk tools on this server →

Across the catalogue

delete_mysql_user on cPanel MCP Server → All critical-risk MCP tools → The MCP Attack Database →

Guides

Govern database agents →Blast radius →Tool call approval →