list_locations
Возвращает список доступных локаций и зон доступности: код локации, ISO-код, список availability_zones. Нужен для выбора location/availability_zone при создании VPS.
This record as markdown: /tools/timeweb-mcp/list-locations.md
What list_locations does on Timeweb
AI agents call list_locations to retrieve information from Timeweb without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why list_locations is rated Low
The tool retrieves configuration metadata (location codes, ISO codes, availability zones) without modifying any state. It is informational only, used to enumerate deployment options before resource creation. No side effects, no data modification, no execution or deletion. This is a classic Read operation with minimal blast radius.
From the tool's definition Tool name 'list_locations' and description states it 'returns a list of available locations and availability zones' (Возвращает список доступных локаций и зон доступности) with codes and parameters. This is a pure query operation for retrieving reference data.
Attacks that exploit this kind of access
The rule that runs list_locations safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Timeweb, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For list_locations, this is the rule to start with:
list_locations 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 Timeweb, apply this rule, and every list_locations call is checked against it from then on.
Questions about list_locations
Возвращает список доступных локаций и зон доступности: код локации, ISO-код, список availability_zones. Нужен для выбора location/availability_zone при создании VPS. It is categorised as a Read tool in the Timeweb MCP Server, which means it retrieves data without modifying state.
Register the Timeweb MCP server in PolicyLayer and add a rule for list_locations: 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 Timeweb. Nothing to install.
list_locations 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_locations 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_locations. 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_locations is provided by the Timeweb MCP server (timeweb-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Timeweb, and thousands of servers like it.
This server
Across the catalogue