codex_delete_user

Remove a user from the organization

SERVERSage MCP SOURCEsagemcp/sagemcp

Critical RISK CLASS

Category Destructive

Parameters 00 required

Recommended Hiddensee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/sagemcp-sagemcp/codex-delete-user.md

WHAT IT DOES

What codex_delete_user does on Sage MCP

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

RISK

Why codex_delete_user is rated Critical

User deletion is an irreversible action that cannot be undone without administrative intervention to restore access. While not data deletion in the traditional sense, removing a user from an organization is a destructive operation that eliminates access rights and potentially associated resources.

From the tool's definition Tool name contains 'delete' and description states 'Remove a user from the organization' - this irreversibly deletes user account access and organizational membership.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs codex_delete_user safely

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

codex_delete_user Hidden

codex_delete_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": [
    "codex_delete_user"
  ]
}

RESTRICT THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about codex_delete_user

What does the codex_delete_user tool do? +

Remove a user from the organization. It is categorised as a Destructive tool in the Sage MCP 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 codex_delete_user? +

Register the Sage MCP server in PolicyLayer and add a rule for codex_delete_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 Sage MCP. Nothing to install.

What risk level is codex_delete_user? +

codex_delete_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 codex_delete_user? +

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

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

codex_delete_user is provided by the Sage MCP server (sagemcp/sagemcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Sage, and thousands of servers like it.

This server

All 359 Sage tools → Critical-risk tools on this server →

Across the catalogue

delete_mysql_user on cPanel MCP Server →sms_delete_message on Twilio SMS MCP Server →delete_snapshot on Why Did You Render →calendar_delete_event on Templonix Lite MCP Server → All critical-risk MCP tools → The MCP Attack Database →

Guides

Govern database agents →Blast radius →Tool call approval →