delete_device
Delete a device/resource (requires write permission). Soft delete by default.
This record as markdown: /tools/io-github-ryanmat-logicmonitor/delete-device.md
What delete_device does on Logicmonitor
AI agents call delete_device 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.
Why delete_device is rated Critical
An AI agent that decides to call delete_device 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
The rule that runs delete_device 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_device, this is the rule to start with:
delete_device is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Logicmonitor, apply this rule, and every delete_device call is checked against it from then on.
Questions about delete_device
Delete a device/resource (requires write permission). Soft delete by default. 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.
Register the Logicmonitor MCP server in PolicyLayer and add a rule for delete_device: 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.
delete_device 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_device 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_device. 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_device 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.
More on Logicmonitor, and thousands of servers like it.
Across the catalogue