edgeconnect_delete_address_group
Delete an EdgeConnect ACL address group by name with write guards.
This record as markdown: /tools/secure-ssid-centralmcp/edgeconnect-delete-address-group.md
What edgeconnect_delete_address_group does on API-Central
AI agents call edgeconnect_delete_address_group 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 edgeconnect_delete_address_group is rated Critical
Deletion of ACL address groups is a destructive action that cannot be undone. While write guards are mentioned as a mitigation, the core function is irreversible data deletion affecting network security configuration. The 'Destructive' category takes precedence over 'Write' because the operation cannot be reversed. High severity due to potential impact on network security rules and configurations.
From the tool's definition Tool name explicitly contains 'delete' and description states 'Delete an EdgeConnect ACL address group by name'. This is an irreversible deletion operation.
Attacks that exploit this kind of access
The rule that runs edgeconnect_delete_address_group 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 edgeconnect_delete_address_group, this is the rule to start with:
edgeconnect_delete_address_group 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 edgeconnect_delete_address_group call is checked against it from then on.
Questions about edgeconnect_delete_address_group
Delete an EdgeConnect ACL address group by name with write guards. 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 edgeconnect_delete_address_group: 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.
edgeconnect_delete_address_group 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 edgeconnect_delete_address_group 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 edgeconnect_delete_address_group. 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.
edgeconnect_delete_address_group 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