delete_glp_role_assignment
Delete an RBAC role assignment by ID.
This record as markdown: /tools/secure-ssid-centralmcp/delete-glp-role-assignment.md
What delete_glp_role_assignment does on API-Central
AI agents call delete_glp_role_assignment 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.
Why delete_glp_role_assignment is rated Critical
This tool performs an irreversible deletion of an RBAC (Role-Based Access Control) role assignment. Deleting role assignments cannot be undone without manual recreation and can immediately revoke user access to network resources, causing operational disruption. This qualifies as Destructive rather than Write because the action cannot be reversed programmatically.
From the tool's definition Tool name contains 'delete'; description states 'Delete an RBAC role assignment by ID.' The action irreversibly removes access control configuration.
Attacks that exploit this kind of access
The rule that runs delete_glp_role_assignment 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 delete_glp_role_assignment, this is the rule to start with:
delete_glp_role_assignment is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect API-Central, apply this rule, and every delete_glp_role_assignment call is checked against it from then on.
Questions about delete_glp_role_assignment
Delete an RBAC role assignment by ID. 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.
Register the API-Central MCP server in PolicyLayer and add a rule for delete_glp_role_assignment: 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.
delete_glp_role_assignment is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the delete_glp_role_assignment 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 delete_glp_role_assignment. 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.
delete_glp_role_assignment 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.
More on API-Central, and thousands of servers like it.
Across the catalogue