delete_recipient_group

Delete a recipient group (requires write permission)

SERVERLogicmonitor SOURCEpypi:lm-mcp

Critical RISK CLASS

Category Destructive

Parameters 00 required

Recommended Hiddensee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-ryanmat-logicmonitor/delete-recipient-group.md

WHAT IT DOES

What delete_recipient_group does on Logicmonitor

AI agents call delete_recipient_group to permanently remove resources in Logicmonitor, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

RISK

Why delete_recipient_group is rated Critical

An AI agent that decides to call delete_recipient_group doesn't hesitate, doesn't double-check, and doesn't stop at one. Whatever it removes from Logicmonitor is gone. There is no undo for destructive operations.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs delete_recipient_group safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Logicmonitor, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For delete_recipient_group, this is the rule to start with:

delete_recipient_group Hidden

delete_recipient_group is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "hide": [
    "delete_recipient_group"
  ]
}

RESTRICT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Logicmonitor, apply this rule, and every delete_recipient_group call is checked against it from then on.

FAQ

Questions about delete_recipient_group

What does the delete_recipient_group tool do? +

Delete a recipient group (requires write permission). It is categorised as a Destructive tool in the Logicmonitor 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_recipient_group? +

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

What risk level is delete_recipient_group? +

delete_recipient_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_recipient_group? +

Yes. Add a rate_limit block to the delete_recipient_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_recipient_group completely? +

Set action: deny in the PolicyLayer policy for delete_recipient_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_recipient_group? +

delete_recipient_group is provided by the Logicmonitor MCP server (pypi:lm-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Logicmonitor, and thousands of servers like it.

This server

All 306 Logicmonitor tools → Critical-risk tools on this server →

Across the catalogue

sms_delete_message on Twilio SMS MCP Server →delete_snapshot on Why Did You Render →calendar_delete_event on Templonix Lite MCP Server →delete_addon_domain on cPanel MCP Server → All critical-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Blast radius →Tool call approval →