Delete an alert group
AI agents call ambari_alerts_deletealertgroup to permanently remove resources in Ambari MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Deleting an alert group destroys monitoring/alerting configuration that cannot be automatically recovered. This is a destructive operation with potential operational impact (loss of alert notifications and definitions tied to that group). While not as critical as deleting production data, it irreversibly removes system configuration state and must be classified as Destructive rather than Write.
From the tool's definition Tool name contains 'delete' and description states 'Delete an alert group'. This irreversibly removes alert group configuration and associations.
Attacks that exploit this kind of access
Delete an alert group. It is categorised as a Destructive tool in the Ambari MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Ambari MCP Server MCP server in PolicyLayer and add a rule for ambari_alerts_deletealertgroup: 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 Ambari MCP Server. Nothing to install.
ambari_alerts_deletealertgroup 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 ambari_alerts_deletealertgroup 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 ambari_alerts_deletealertgroup. 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.
ambari_alerts_deletealertgroup is provided by the Ambari MCP Server MCP server (nikita15p/ambari-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →