delete_notification_rule
Delete a notification rule by ID. UNCONFIRMED endpoint shape — see module note above.
This record as markdown: /tools/secure-ssid-centralmcp/delete-notification-rule.md
What delete_notification_rule does on API-Central
AI agents call delete_notification_rule to permanently remove resources in API-Central, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why delete_notification_rule is rated Critical
This tool permanently removes a notification rule configuration by its identifier, which cannot be undone. Deletion of infrastructure monitoring rules could disable critical alerts, potentially leaving security incidents or operational issues undetected. While not as immediately severe as deleting devices or network configuration, removing notification rules is an irreversible action with operational blast radius.
From the tool's definition Tool name contains 'delete_notification_rule' — the verb 'delete' explicitly indicates irreversible removal of data (a notification rule). Description confirms: 'Delete a notification rule by ID.'
Attacks that exploit this kind of access
The rule that runs delete_notification_rule safely
PolicyLayer is an MCP gateway: it sits between your AI agents and API-Central, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For delete_notification_rule, this is the rule to start with:
delete_notification_rule 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 API-Central, apply this rule, and every delete_notification_rule call is checked against it from then on.
Questions about delete_notification_rule
Delete a notification rule by ID. UNCONFIRMED endpoint shape — see module note above. It is categorised as a Destructive tool in the API-Central MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the API-Central MCP server in PolicyLayer and add a rule for delete_notification_rule: 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 API-Central. Nothing to install.
delete_notification_rule 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_notification_rule 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_notification_rule. 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_notification_rule is provided by the API-Central MCP server (secure-ssid/centralmcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on API-Central, and thousands of servers like it.
Across the catalogue