apstra_delete_connectivity_template
Delete one Apstra connectivity template by ID.
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.
Attacks that exploit this kind of access
The rule that runs apstra_delete_connectivity_template 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 apstra_delete_connectivity_template, this is the rule to start with:
apstra_delete_connectivity_template 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 apstra_delete_connectivity_template call is checked against it from then on.
Questions about apstra_delete_connectivity_template
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.
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.
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.
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.
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.
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.
Across the catalogue