alert_restore

Restore a previously dismissed alert by its UUID, making it active again.

SERVERNasbridge SOURCEmaverick0628/nasbridge

Medium RISK CLASS

Category Write

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/nasbridge/alert-restore.md

WHAT IT DOES

What alert_restore does on Nasbridge

AI agents use alert_restore to create or update resources in Nasbridge, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Nasbridge environment.

RISK

Why alert_restore is rated Medium

This tool modifies existing data (alert state) reversibly by changing a dismissed alert back to active status. It does not delete, execute code, or cause financial impact. The severity is medium because restoring alerts could cause operational disruption or unwanted notifications, but the action is reversible and localized to alert management.

From the tool's definition Tool name 'alert_restore' and description 'Restore a previously dismissed alert by its UUID, making it active again' indicates modification of alert state from dismissed to active.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

alert_restore Rate-limited

alert_restore stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "alert_restore": {
      "limits": [
        {
          "counter": "alert_restore_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about alert_restore

What does the alert_restore tool do? +

Restore a previously dismissed alert by its UUID, making it active again. It is categorised as a Write tool in the Nasbridge MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on alert_restore? +

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

What risk level is alert_restore? +

alert_restore is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit alert_restore? +

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

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

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

KEEP EXPLORING

More on Nasbridge, and thousands of servers like it.

This server

All 279 Nasbridge tools →

Across the catalogue

The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →