delete_glp_scope_group
Delete an RBAC scope group by ID.
This record as markdown: /tools/secure-ssid-centralmcp/delete-glp-scope-group.md
What delete_glp_scope_group does on API-Central
AI agents call delete_glp_scope_group 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_scope_group is rated Critical
Deleting an RBAC scope group is a destructive action that cannot be undone and removes access control configurations. This affects network security and user permissions. While not directly financial, the blast radius is high if an AI agent mistakenly deletes critical access control groups, potentially disrupting network operations or creating security gaps. Destructive category takes precedence over Write or Execute.
From the tool's definition Tool name contains 'delete' and description states 'Delete an RBAC scope group by ID' — this is an irreversible deletion operation.
Attacks that exploit this kind of access
The rule that runs delete_glp_scope_group 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_scope_group, this is the rule to start with:
delete_glp_scope_group 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_scope_group call is checked against it from then on.
Questions about delete_glp_scope_group
Delete an RBAC scope group 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_scope_group: 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_scope_group 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_scope_group 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_scope_group. 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_scope_group 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