alertservice_delete
Delete an alert notification service by its ID. Use alertservice_list to find the ID.
This record as markdown: /tools/nasbridge/alertservice-delete.md
What alertservice_delete does on Nasbridge
AI agents call alertservice_delete to permanently remove resources in Nasbridge, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why alertservice_delete is rated Critical
The tool performs a destructive operation that permanently removes an alert service configuration. While not data-loss in the sense of user files, deletion of infrastructure configuration is irreversible and could result in loss of monitoring/alerting capabilities.
From the tool's definition Tool description explicitly states 'Delete an alert notification service by its ID' — this is an irreversible deletion of configuration data that cannot be undone without manual recreation.
Attacks that exploit this kind of access
The rule that runs alertservice_delete safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Nasbridge, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For alertservice_delete, this is the rule to start with:
alertservice_delete 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 Nasbridge, apply this rule, and every alertservice_delete call is checked against it from then on.
Questions about alertservice_delete
Delete an alert notification service by its ID. Use alertservice_list to find the ID. It is categorised as a Destructive tool in the Nasbridge MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Nasbridge MCP server in PolicyLayer and add a rule for alertservice_delete: 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 Nasbridge. Nothing to install.
alertservice_delete 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 alertservice_delete 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 alertservice_delete. 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.
alertservice_delete is provided by the Nasbridge MCP server (maverick0628/nasbridge). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Nasbridge, and thousands of servers like it.
Across the catalogue