set_site_alert

SERVERMcp Server SOURCEhttps://dchub.cloud/mcp

Medium RISK CLASS

Category Write

Parameters 40 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/cloud-dchub-mcp-server/set-site-alert.md

WHAT IT DOES

What set_site_alert does on Mcp Server

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

Parameter	Type	Required	Description
`threshold`	number	—	The points/MW move that fires the alert (default 5)
`notify_email`	string	—	Email address the alert is sent to (required); on free tier forced to your human's bound email
`trigger_type`	string	—	What movement fires the alert: "dcpi_change" (default), "capacity_change", or "new_facility_nearby"
`saved_site_id`	object	—	The saved_site_id returned by save_site or list_saved_sites (required)

Parameters from the server's own tool schema.

RISK

Why set_site_alert is rated Medium

This tool creates a new alert/watch configuration on a saved site, which is a reversible write operation (alerts can typically be disabled or deleted). It does not execute external code, delete data permanently, move money, or retrieve data without side effects. The trigger mechanism that monitors for changes is a side effect of writing the alert configuration, but the primary action is configuration creation.

From the tool's definition The tool arms an email watch on a site by setting up alerts, which creates and modifies a monitoring configuration. Key phrases: 'Arm an email watch', 'emails you when...move', 'call set_site_alert on that id'.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs set_site_alert safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Mcp Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For set_site_alert, this is the rule to start with:

set_site_alert Rate-limited

set_site_alert 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": {
    "set_site_alert": {
      "limits": [
        {
          "counter": "set_site_alert_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 Mcp Server, apply this rule, and every set_site_alert call is checked against it from then on.

FAQ

Questions about set_site_alert

What does the set_site_alert tool do? +

Arm an email watch on a site you already saved (FREE with a key) — DC Hub emails you when that site’s DCPI score, grid capacity, or nearby facilities move, so you don’t have to keep re-checking. On the free tier the alert is delivered to your human’s bound email (call bind_email first; notify_email is forced to that address). Pro can send to any address. The "monitor my shortlist for me" loop: call save_site first (it returns a saved_site_id), then set_site_alert on that id. Params: saved_site_id (required integer, from save_site or list_saved_sites), trigger_type ("dcpi_change" | "capacity_change" | "new_facility_nearby", default "dcpi_change"), threshold (number — the points/MW move that fires it, default 5), notify_email (required — the address the alert is sent to). Try: set_site_alert saved_site_id=12 trigger_type=dcpi_change threshold=5 notify_email=you@firm.com. Returns {ok, alert_id, message}. Do NOT use to watch a whole MARKET (use set_market_alert) or to save a new site (use save_site); this arms a monitor on ONE already-saved site. It is categorised as a Write tool in the Mcp Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

What parameters does set_site_alert accept? +

set_site_alert accepts 4 parameters: threshold, notify_email, trigger_type, saved_site_id. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on set_site_alert? +

Register the Mcp Server MCP server in PolicyLayer and add a rule for set_site_alert: 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 Mcp Server. Nothing to install.

What risk level is set_site_alert? +

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

Can I rate-limit set_site_alert? +

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

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

set_site_alert is provided by the Mcp Server MCP server (https://dchub.cloud/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Mcp Server, and thousands of servers like it.

This server

All 79 Mcp Server tools →

Across the catalogue

set-prioity on Kanban MCP Server →team_manager_set_sources on Team Manager MCP →qt_set_property on Qt → The MCP Attack Database →

Guides

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