list_projects
Возвращает список всех проектов аккаунта с id, именем, описанием и флагом по умолчанию. Используй перед работой с ресурсами проекта, чтобы получить project_id.
This record as markdown: /tools/timeweb-mcp/list-projects.md
What list_projects does on Timeweb
AI agents call list_projects 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_projects is rated Low
This tool queries and retrieves account project data without modification, deletion, or side effects. It is purely informational and used to enumerate resources. No data is created, modified, or destroyed. This is a classic Read operation with low blast radius — the worst outcome of misuse would be information disclosure about project structure.
From the tool's definition Tool name 'list_projects' and description 'Возвращает список всех проектов аккаунта' (returns list of all projects in account) indicates a retrieval operation that returns project metadata (id, name, description, default flag).
Attacks that exploit this kind of access
The rule that runs list_projects 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_projects, this is the rule to start with:
list_projects 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_projects call is checked against it from then on.
Questions about list_projects
Возвращает список всех проектов аккаунта с id, именем, описанием и флагом по умолчанию. Используй перед работой с ресурсами проекта, чтобы получить project_id. 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_projects: 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_projects 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_projects 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_projects. 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_projects 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