delete_check_group

Delete a check group. All checks in the group will be moved to ungrouped.

Server Pingera MCP Server pingera/pingera-mcp
Category Destructive
Risk class Critical
Parameters 00 required

What delete_check_group does on Pingera MCP Server

AI agents call delete_check_group to permanently remove resources in Pingera MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

Why delete_check_group needs a policy

Deleting a check group is a destructive action that cannot be undone. While the checks themselves are preserved (moved to ungrouped), the group structure and its organizational metadata are permanently erased. This is irreversible and represents data loss. High severity because misconfiguration or accidental invocation by an AI agent could disrupt monitoring organization and lose administrative grouping context.

From the tool's definition Tool name contains 'delete' and description states 'Delete a check group' — an irreversible operation that removes a monitoring configuration.

Questions about delete_check_group

What does the delete_check_group tool do? +

Delete a check group. All checks in the group will be moved to ungrouped. It is categorised as a Destructive tool in the Pingera MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on delete_check_group? +

Register the Pingera MCP Server MCP server in PolicyLayer and add a rule for delete_check_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 Pingera MCP Server. Nothing to install.

What risk level is delete_check_group? +

delete_check_group is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit delete_check_group? +

Yes. Add a rate_limit block to the delete_check_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.

How do I block delete_check_group completely? +

Set action: deny in the PolicyLayer policy for delete_check_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.

What MCP server provides delete_check_group? +

delete_check_group is provided by the Pingera MCP Server MCP server (pingera/pingera-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// LOOK UP ANOTHER 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 →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.