generate_site_analysis
Use when a user wants a SHAREABLE, branded multi-page Site Analysis PDF for ONE lat/lon (a powered-land parcel, a candidate campus) — the polished client deliverable, not just a score. Example: "Make the Site Analysis PDF for this Carrier Mills parcel, 150 MW, for TON Infrastructure." — generate_...
This record as markdown: /tools/cloud-dchub-mcp-server/generate-site-analysis.md
What generate_site_analysis does on Mcp Server
AI agents use generate_site_analysis 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, required), e.g. 37.694 |
lng | number | — | Alias for lon — either name works |
lon | number | — | Site longitude in decimal degrees (-180 to 180, required), e.g. -88.65 |
latitude | number | — | Alias for lat — either name works |
use_case | string | — | Optional workload descriptor to tailor the report, e.g. "AI training campus" |
longitude | number | — | Alias for lon — either name works |
capacity_mw | number | — | Target power load for the build in megawatts (MW), e.g. 150 (typical 50-500) |
prepared_by | string | — | Your firm name that brands the report; defaults to DC Hub, e.g. "Martone Advisors" |
prepared_for | string | — | Client name printed on the report cover, e.g. "TON Infrastructure" |
latency_target | string | — | Optional metro to measure latency against; default = nearest real carrier hotel |
Parameters from the server's own tool schema.
Why generate_site_analysis is rated Medium
Creates and produces a formatted document artifact; reversible output with no destructive or financial consequences.
From the tool's definition generates multi-page branded PDF deliverable for client
Risk signalsHigh parameter count (10 properties)
Attacks that exploit this kind of access
The rule that runs generate_site_analysis 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 generate_site_analysis, this is the rule to start with:
generate_site_analysis 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Mcp Server, apply this rule, and every generate_site_analysis call is checked against it from then on.
Questions about generate_site_analysis
Use when a user wants a SHAREABLE, branded multi-page Site Analysis PDF for ONE lat/lon (a powered-land parcel, a candidate campus) — the polished client deliverable, not just a score. Example: "Make the Site Analysis PDF for this Carrier Mills parcel, 150 MW, for TON Infrastructure." — generate_site_analysis lat=37.694 lon=-88.65 capacity_mw=150 prepared_for="TON Infrastructure" prepared_by="Martone Advisors". Params: lat (-90 to 90, required), lon (-180 to 180, required), capacity_mw (target load MW, e.g. 50-500), prepared_for (client name on the cover), prepared_by (your firm — brands the report; defaults to DC Hub), latency_target (optional metro override; default = nearest real carrier hotel). Returns: {survey:{verdict, power/transmission, gas, water, air-permitting, fiber carriers, latency-to-nearest-carrier-hotel, market, tax}, pdf_report_url}. pdf_report_url is a ready-to-open link to download the branded 5-page PDF — no login needed, valid ~7 days; hand it to your human. For just the numeric suitability score (no PDF), use analyze_site instead. 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.
generate_site_analysis accepts 10 parameters: lat, lng, lon, latitude, use_case, longitude, capacity_mw, prepared_by, prepared_for, latency_target. The full parameter table on this page comes from the server's own tool schema.
Register the Mcp Server MCP server in PolicyLayer and add a rule for generate_site_analysis: 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.
generate_site_analysis is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the generate_site_analysis 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 generate_site_analysis. 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.
generate_site_analysis 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.
More on Mcp Server, and thousands of servers like it.
This server
Across the catalogue