delete_authz_policy

Delete a CNAC authz policy by ID.

Server API-Central secure-ssid/centralmcp
Category Destructive
Risk class Critical
Parameters 00 required

What delete_authz_policy does on API-Central

AI agents call delete_authz_policy 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_authz_policy needs a policy

This tool irreversibly deletes authorization policy configurations. Deletion of authz policies cannot be undone and directly impacts network security posture by removing access control rules. This is a destructive operation with potentially significant blast radius if an AI agent misuses the ID parameter, inadvertently removing critical security policies that protect the network infrastructure.

From the tool's definition The tool name explicitly contains 'delete' and the description states 'Delete a CNAC authz policy by ID.' CNAC (Clearpass Network Access Control) authorization policies are security-critical configurations that control network access permissions.

Questions about delete_authz_policy

What does the delete_authz_policy tool do? +

Delete a CNAC authz policy 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.

How do I enforce a policy on delete_authz_policy? +

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

delete_authz_policy 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_authz_policy? +

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

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

delete_authz_policy 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.

// THE FULL RECORD

delete_authz_policy is one line of API-Central's registry record.

The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.