New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

apstra_delete_connectivity_template

Delete one Apstra connectivity template by ID.

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/apstra-delete-connectivity-template.md

What apstra_delete_connectivity_template does on API-Central

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

The tool permanently removes a connectivity template, which cannot be undone. In a network infrastructure context (HPE Aruba Central), deleting connectivity templates could disrupt network configurations and require recovery from backups. This is irreversible data destruction, placing it in the Destructive category with high severity due to potential impact on network operations.

From the tool's definition Tool name contains 'delete' and description states 'Delete one Apstra connectivity template by ID.' This is an irreversible deletion operation.

Questions about apstra_delete_connectivity_template

What does the apstra_delete_connectivity_template tool do? +

Delete one Apstra connectivity template 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 apstra_delete_connectivity_template? +

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

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

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

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

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

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of API-Central's. Pull the full record:

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.