Delete a monitor group.
AI agents call delete_monitor_group to permanently remove resources in Pipiads — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
| Parameter | Type | Required | Description |
|---|---|---|---|
group_id | string | Yes | Group ID to delete |
Parameters from the server's own tool schema.
This tool permanently removes a monitor group, which is a destructive operation that cannot be undone. Although the blast radius is somewhat limited to a specific monitoring configuration rather than production data, the irreversibility of deletion and potential loss of monitoring setup justifies the Destructive category and high severity.
From the tool's definition Tool name is 'delete_monitor_group' with description 'Delete a monitor group.' The verb 'delete' explicitly indicates irreversible removal of data.
Attacks that exploit this kind of access
Delete a monitor group. It is categorised as a Destructive tool in the Pipiads MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
delete_monitor_group accepts 1 parameter: group_id. Required: group_id. The full parameter table on this page comes from the server's own tool schema.
Register the Pipiads MCP server in PolicyLayer and add a rule for delete_monitor_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 Pipiads. Nothing to install.
delete_monitor_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 delete_monitor_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 delete_monitor_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.
delete_monitor_group is provided by the Pipiads MCP server (pipiads-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 →