delete_role

A destructive tool on the API-Central MCP server.

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/delete-role.md

WHAT IT DOES

What delete_role does on API-Central

AI agents call delete_role 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 delete_role is rated Critical

Role deletion is an irreversible operation that removes access control definitions from the system. This has high blast radius in network operations: an AI agent deleting critical roles could lock out administrators, disrupt security policies, or leave the system in an inconsistent state.

From the tool's definition Tool name is 'delete_role' with no description provided. The 'delete' verb indicates irreversible removal of data. In a network operations context (HPE Aruba Central), deleting a role removes access control definitions that cannot be easily recovered.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs delete_role 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_role, this is the rule to start with:

delete_role Hidden

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

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 delete_role call is checked against it from then on.

FAQ

Questions about delete_role

What does the delete_role tool do? +

delete_role is a destructive tool on the API-Central MCP server. 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 delete_role? +

Register the API-Central MCP server in PolicyLayer and add a rule for delete_role: 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 delete_role? +

delete_role 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 delete_role? +

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

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

delete_role 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

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

Guides

Govern database agents →Blast radius →Tool call approval →