clearpass_delete_guest
Delete a ClearPass guest account by username or ID.
This record as markdown: /tools/secure-ssid-centralmcp/clearpass-delete-guest.md
What clearpass_delete_guest does on API-Central
AI agents call clearpass_delete_guest 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 clearpass_delete_guest is rated Critical
This tool permanently removes guest accounts from the ClearPass system. Deletion is irreversible and could disrupt network access for legitimate guests if misused by an AI agent. While not financial, the destructive nature of account deletion (cannot be undone without manual recreation) makes it more severe than Write operations.
From the tool's definition "Delete a ClearPass guest account by username or ID" - the tool explicitly deletes guest accounts, which is an irreversible operation that removes user access and authentication records.
Attacks that exploit this kind of access
The rule that runs clearpass_delete_guest 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 clearpass_delete_guest, this is the rule to start with:
clearpass_delete_guest 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 clearpass_delete_guest call is checked against it from then on.
Questions about clearpass_delete_guest
Delete a ClearPass guest account by username or 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 clearpass_delete_guest: 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.
clearpass_delete_guest 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 clearpass_delete_guest 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 clearpass_delete_guest. 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.
clearpass_delete_guest 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