get_vpcs
Получает список всех виртуальных частных сетей (VPC) пользователя
This record as markdown: /tools/timeweb-mcp/get-vpcs.md
What get_vpcs does on Timeweb
AI agents call get_vpcs 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 get_vpcs is rated Low
This is a straightforward read operation that queries and returns data about the user's VPC resources. It has no side effects, does not modify infrastructure, execute code, or commit financial changes. The verb 'get' and the retrieval nature of listing VPCs confirms it belongs in the Read category with low severity, as it only exposes existing configuration data.
From the tool's definition Tool name 'get_vpcs' and description 'Получает список всех виртуальных частных сетей (VPC) пользователя' (Retrieves a list of all user's virtual private networks) indicate a retrieval operation with no modification or execution of external operations.
Attacks that exploit this kind of access
The rule that runs get_vpcs 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 get_vpcs, this is the rule to start with:
get_vpcs 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 get_vpcs call is checked against it from then on.
Questions about get_vpcs
Получает список всех виртуальных частных сетей (VPC) пользователя. 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 get_vpcs: 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.
get_vpcs 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_vpcs 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_vpcs. 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_vpcs 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