Delete an adapter configuration policy
AI agents call delete_adapter_config_policy to permanently remove resources in Intersight MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool performs a destructive operation that permanently removes a policy object from the system. Deletion cannot be reversed and would cause loss of configuration data. While not as critical as deleting running systems, removing policies can disrupt infrastructure management and require administrative recovery.
From the tool's definition Tool name 'delete_adapter_config_policy' and description 'Delete an adapter configuration policy' explicitly indicate irreversible deletion of a configuration policy resource.
Documented attack patterns abuse exactly the kind of access delete_adapter_config_policy gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Intersight MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for delete_adapter_config_policy:
{
"version": "1",
"default": "deny",
"hide": [
"delete_adapter_config_policy"
]
}delete_adapter_config_policy disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.
Free to start. No card required.
Delete an adapter configuration policy. It is categorised as a Destructive tool in the Intersight MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Intersight MCP Server MCP server in PolicyLayer and add a rule for delete_adapter_config_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 Intersight MCP Server. Nothing to install.
delete_adapter_config_policy 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_adapter_config_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.
Set action: deny in the PolicyLayer policy for delete_adapter_config_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.
delete_adapter_config_policy is provided by the Intersight MCP Server MCP server (jim-coyne/intersight_mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Intersight MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
198 Intersight MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.