save_site

SERVERMcp Server SOURCEhttps://dchub.cloud/mcp

Medium RISK CLASS

Category Write

Parameters 100 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/save-site.md

WHAT IT DOES

What save_site does on Mcp Server

AI agents use save_site 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
`lat`	number	—	Site latitude in decimal degrees (-90 to 90), e.g. 39.04
`lng`	number	—	Alias for lon — either name works
`lon`	number	—	Site longitude in decimal degrees (-180 to 180), e.g. -77.48
`name`	string	—	Optional label for the saved site, e.g. "Ashburn parcel"
`notes`	string	—	Optional free-text notes to store with the saved site
`state`	string	—	US state abbreviation for the site, e.g. VA
`market`	string	—	Market slug (metro) the site belongs to, e.g. northern-virginia
`latitude`	number	—	Alias for lat — either name works
`longitude`	number	—	Alias for lon — either name works
`target_mw`	number	—	Target power load for the planned build in megawatts (MW), e.g. 100

Parameters from the server's own tool schema.

RISK

Why save_site is rated Medium

An AI agent can call save_site faster than any human can review: one bad instruction and it creates or modifies resources in Mcp Server by the hundred, each call as confident as the last.

Risk signalsHigh parameter count (10 properties) · Bulk/mass operation — affects multiple targets

Attacks that exploit this kind of access

RECOMMENDED RULE

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

save_site Rate-limited

save_site 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": {
    "save_site": {
      "limits": [
        {
          "counter": "save_site_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 save_site call is checked against it from then on.

FAQ

Questions about save_site

What does the save_site tool do? +

Save a candidate data-center site to your DC Hub account to track it across sessions (FREE — just needs a key; call claim_free_key if you don't have one). Give lat + lon (plus optional name, state, market, target_mw, notes). Returns the saved site id. Pass market and DC Hub snapshots the site's DCPI baseline at save time, so every later list_saved_sites / get_changes shows how ITS score and verdict moved since you saved it. Builds a persistent shortlist an agent can revisit + monitor — after saving, pass the returned id to set_site_alert so DC Hub emails you when that site’s DCPI/capacity/nearby-facilities move (no re-checking). Try: save_site lat=39.04 lon=-77.48 name="Ashburn parcel" market=northern-virginia target_mw=100. Do NOT use to read back the shortlist (use list_saved_sites), download it (use export_dataset), or score a site (use score_facility); this WRITES one site to your account. 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 save_site accept? +

save_site accepts 10 parameters: lat, lng, lon, name, notes, state, market, latitude, longitude, target_mw. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on save_site? +

Register the Mcp Server MCP server in PolicyLayer and add a rule for save_site: 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 save_site? +

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

Can I rate-limit save_site? +

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

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

save_site 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

save_snapshot on Why Did You Render →save_tags on Mcptube Vision → The MCP Attack Database →

Guides

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