clear_alerts

Clear one or more alerts by key. Returns the Central async task payload.

SERVERAPI-Central SOURCEsecure-ssid/centralmcp

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/secure-ssid-centralmcp/clear-alerts.md

WHAT IT DOES

What clear_alerts does on API-Central

AI agents call clear_alerts 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.

RISK

Why clear_alerts is rated Critical

Clearing alerts destroys audit/monitoring history and cannot be undone. An AI agent misusing this tool could suppress critical network alerts, hiding ongoing incidents or security events. This is irreversible data removal, placing it in the Destructive category rather than Write.

From the tool's definition 'Clear one or more alerts by key' — clearing alerts is an irreversible operation that permanently removes alert records from the system

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs clear_alerts 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 clear_alerts, this is the rule to start with:

clear_alerts Hidden

clear_alerts 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": [
    "clear_alerts"
  ]
}

RESTRICT THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about clear_alerts

What does the clear_alerts tool do? +

Clear one or more alerts by key. Returns the Central async task payload. 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.

How do I enforce a policy on clear_alerts? +

Register the API-Central MCP server in PolicyLayer and add a rule for clear_alerts: 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.

What risk level is clear_alerts? +

clear_alerts 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 clear_alerts? +

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

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

clear_alerts 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.

KEEP EXPLORING

More on API-Central, and thousands of servers like it.

This server

All 590 API-Central tools → Critical-risk tools on this server →

Across the catalogue

clear_renders on Why Did You Render →knowledge_clear on Templonix Lite MCP Server →clear_scan on Frida Game Hacking MCP →clear_spam_box on cPanel MCP Server → All critical-risk MCP tools → The MCP Attack Database →

Guides

Govern database agents →Blast radius →Tool call approval →