delete_config_assignment
A destructive tool on the Hpe Networking MCP server.
This record as markdown: /tools/hpe-networking-mcp/delete-config-assignment.md
What delete_config_assignment does on Hpe Networking
AI agents call delete_config_assignment to permanently remove resources in Hpe Networking, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why delete_config_assignment is rated Critical
The 'delete' verb combined with 'config_assignment' in a network management system indicates this tool permanently removes configuration assignments from devices or groups. This is destructive by definition—deletion of network configurations is irreversible and impacts live infrastructure. Severity is high because misconfiguration deletions could disrupt network operations across multiple devices.
From the tool's definition Tool name 'delete_config_assignment' explicitly includes 'delete', indicating irreversible removal of configuration data. In a network operations context, deleting assignments affects device configurations and cannot be undone without restoration processes.
Attacks that exploit this kind of access
The rule that runs delete_config_assignment safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Hpe Networking, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For delete_config_assignment, this is the rule to start with:
delete_config_assignment 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 Hpe Networking, apply this rule, and every delete_config_assignment call is checked against it from then on.
Questions about delete_config_assignment
delete_config_assignment is a destructive tool on the Hpe Networking MCP server. It is categorised as a Destructive tool in the Hpe Networking MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Hpe Networking MCP server in PolicyLayer and add a rule for delete_config_assignment: 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 Hpe Networking. Nothing to install.
delete_config_assignment 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 delete_config_assignment 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 delete_config_assignment. 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.
delete_config_assignment is provided by the Hpe Networking MCP server (secure-ssid/hpe-networking-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Hpe Networking, and thousands of servers like it.
Across the catalogue