Lists cities with curated baseline climate data. Other cities still work via fallback.
AI agents call list_supported_cities to retrieve information from Ts Mcp Starter without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and returns a list of supported cities with baseline climate data. It is a pure read operation that retrieves information without modifying, creating, deleting, or executing any external actions. The low severity reflects minimal security risk: knowing supported cities poses no blast radius to system integrity, data safety, or user operations.
From the tool's definition Tool name is 'list_supported_cities' and description states it 'Lists cities' — a retrieval operation with no side effects or data modification.
Attacks that exploit this kind of access
Lists cities with curated baseline climate data. Other cities still work via fallback. It is categorised as a Read tool in the Ts Mcp Starter MCP Server, which means it retrieves data without modifying state.
Register the Ts Mcp Starter MCP server in PolicyLayer and add a rule for list_supported_cities: 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 Ts Mcp Starter. Nothing to install.
list_supported_cities 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 list_supported_cities 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 list_supported_cities. 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.
list_supported_cities is provided by the Ts Mcp Starter MCP server (shawntyn/ts-mcp-starter). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →