disassociate_glp_user

Remove (disassociate) a user from the GLP workspace.

SERVERAPI-Central SOURCEsecure-ssid/centralmcp

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/secure-ssid-centralmcp/disassociate-glp-user.md

WHAT IT DOES

What disassociate_glp_user does on API-Central

AI agents call disassociate_glp_user to permanently remove resources in API-Central, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

RISK

Why disassociate_glp_user is rated Critical

Disassociating a user from a workspace is an irreversible removal of access/membership. It cannot be undone automatically — re-associating requires explicit re-invitation or re-provisioning. Misuse by an AI agent could lock out legitimate users from the GreenLake Platform workspace, causing significant operational disruption.

From the tool's definition Remove (disassociate) a user from the GLP workspace

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs disassociate_glp_user safely

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

disassociate_glp_user Hidden

disassociate_glp_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": [
    "disassociate_glp_user"
  ]
}

RESTRICT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect API-Central, apply this rule, and every disassociate_glp_user call is checked against it from then on.

FAQ

Questions about disassociate_glp_user

What does the disassociate_glp_user tool do? +

Remove (disassociate) a user from the GLP workspace. It is categorised as a Destructive tool in the API-Central 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 disassociate_glp_user? +

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

What risk level is disassociate_glp_user? +

disassociate_glp_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 disassociate_glp_user? +

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

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

disassociate_glp_user is provided by the API-Central MCP server (secure-ssid/centralmcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on API-Central, and thousands of servers like it.

This server

All 590 API-Central 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 →