remove_mssql_user

Remove user from MSSQL database

SERVER20i MCP Server SOURCEcbrown35/20i-mcp

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/cbrown35-20i-mcp/remove-mssql-user.md

WHAT IT DOES

What remove_mssql_user does on 20i MCP Server

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

RISK

Why remove_mssql_user is rated Critical

Removing a database user is a destructive operation that irreversibly deletes access credentials and user identity from the MSSQL system. While it does not delete data directly, it constitutes permanent removal of a system resource.

From the tool's definition Tool name 'remove_mssql_user' combined with description 'Remove user from MSSQL database' indicates irreversible deletion of a database user account.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs remove_mssql_user safely

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

remove_mssql_user Hidden

remove_mssql_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": [
    "remove_mssql_user"
  ]
}

RESTRICT THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about remove_mssql_user

What does the remove_mssql_user tool do? +

Remove user from MSSQL database. It is categorised as a Destructive tool in the 20i 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 remove_mssql_user? +

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

What risk level is remove_mssql_user? +

remove_mssql_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 remove_mssql_user? +

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

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

remove_mssql_user is provided by the 20i MCP Server MCP server (cbrown35/20i-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

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

This server

All 302 20i MCP Server tools → Critical-risk tools on this server →

Across the catalogue

remove_video on Mcptube Vision →delete_mysql_user on cPanel MCP Server →remove_concept on MegaMemory →task_assignees_remove on Vikunja → All critical-risk MCP tools → The MCP Attack Database →

Guides

Govern database agents →Blast radius →Tool call approval →