get_composite_site_score

SERVERMcp Server SOURCEhttps://dchub.cloud/mcp

Low RISK CLASS

Category Read

Parameters 60 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/cloud-dchub-mcp-server/get-composite-site-score.md

WHAT IT DOES

What get_composite_site_score does on Mcp Server

AI agents call get_composite_site_score to retrieve information from Mcp Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Parameter	Type	Required	Description
`lat`	number	—	Site latitude in decimal degrees (-90 to 90, required), e.g. 33.45
`lng`	number	—	Alias for lon — either name works
`lon`	number	—	Site longitude in decimal degrees (-180 to 180, required), e.g. -112.07
`state`	string	—	US state abbreviation (optional) — improves water/context lookups, e.g. AZ
`latitude`	number	—	Alias for lat — either name works
`longitude`	number	—	Alias for lon — either name works

Parameters from the server's own tool schema.

RISK

Why get_composite_site_score is rated Low

Even though get_composite_site_score only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

get_composite_site_score Allowed

get_composite_site_score is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_composite_site_score": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about get_composite_site_score

What does the get_composite_site_score tool do? +

Use when a user wants ONE honest 0-100 site suitability/risk verdict for a lat/lon WITH an explicit per-factor coverage map — which factors are actually measured vs. declared unavailable. Unlike analyze_site (full raw data dump), this scores ONLY over VALIDATED factors and never imputes a missing one: power/grid, fiber, natural-hazard risk (FEMA NRI) and water (live WRI Aqueduct 4.0 baseline water stress) are all live; water is "unavailable" only outside basin coverage (never faked); market/DCPI is v1-unavailable (use rank_markets). Example: get_composite_site_score lat=33.45 lon=-112.07 state=AZ. Returns {composite_score (0-100 over validated factors), verdict (BUILD/CAUTION/AVOID), confidence (complete|conditional), coverage {power_grid|fiber|water|risk_resilience|market_dcpi: validated|unavailable}, coverage_ratio, sub_scores, caveats}. Use analyze_site for full data, compare_sites for 2-4 sites, rank_markets for whole-market ranking. It is categorised as a Read tool in the Mcp Server MCP Server, which means it retrieves data without modifying state.

What parameters does get_composite_site_score accept? +

get_composite_site_score accepts 6 parameters: lat, lng, lon, state, latitude, longitude. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on get_composite_site_score? +

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

get_composite_site_score is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_composite_site_score? +

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

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

get_composite_site_score 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

get_cocktail_by_category on Cocktails RAG MCP Server →get_torrent_detail on M-Team MCP Server →aiva_get_affiliate on AIVA MCP Server →get-chuck-categories on Jokes MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →