get_shortlist
Retrieve a saved shortlist (Phase 5). With refresh=true (default) each site is RE-SCORED against the current national percentile baseline and returns saved_score, current_score, and score_delta_since_saved — so you see whether a site slipped because IT changed or the POPULATION did. The reliable ...
This record as markdown: /tools/cloud-dchub-mcp-server/get-shortlist.md
What get_shortlist does on Mcp Server
AI agents call get_shortlist 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 |
|---|---|---|---|
name | string | — | The shortlist name to fetch |
refresh | boolean | — | true (default) = re-score every site against the CURRENT baseline + return drift deltas; false = return the saved snapshots only |
Parameters from the server's own tool schema.
Why get_shortlist is rated Low
This tool queries and retrieves a previously saved shortlist of facilities with optional scoring recalculation against current baselines. The re-scoring is a read-time computation that returns comparative metrics (saved_score, current_score, score_delta_since_saved) without modifying the persisted shortlist itself. No data is created, modified, deleted, or destroyed.
From the tool's definition Tool description explicitly uses 'Retrieve' and 'returns' language indicating data retrieval with no modification. The refreshing functionality re-scores existing data but does not create, delete, or modify the underlying shortlist.
Attacks that exploit this kind of access
The rule that runs get_shortlist 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_shortlist, this is the rule to start with:
get_shortlist is read-only, so it stays allowed. 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 get_shortlist call is checked against it from then on.
Questions about get_shortlist
Retrieve a saved shortlist (Phase 5). With refresh=true (default) each site is RE-SCORED against the current national percentile baseline and returns saved_score, current_score, and score_delta_since_saved — so you see whether a site slipped because IT changed or the POPULATION did. The reliable way to maintain a siting campaign across days/weeks. Scoped to your API key. It is categorised as a Read tool in the Mcp Server MCP Server, which means it retrieves data without modifying state.
get_shortlist accepts 2 parameters: name, refresh. 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 get_shortlist: 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.
get_shortlist is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_shortlist 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 get_shortlist. 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.
get_shortlist 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