This record as markdown: /tools/timeweb-mcp/list-project-databases.md
What list_project_databases does on Timeweb
AI agents call list_project_databases 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.
| Parameter | Type | Required | Description |
|---|---|---|---|
project_id | number | Yes | ОБЯЗАТЕЛЬНОЕ ПОЛЕ - ID проекта |
Parameters from the server's own tool schema.
Why list_project_databases is rated Low
This tool retrieves information about managed databases within a project. It performs a read-only query operation with no side effects, data modification, or resource alteration. The blast radius is minimal as it only returns information the user likely already has access to within their own project.
From the tool's definition Tool name is 'list_project_databases' and description translates to 'List of managed databases in the specified project.' The verb 'list' and the function of retrieving/querying database information with no modification capability.
Attacks that exploit this kind of access
The rule that runs list_project_databases 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_project_databases, this is the rule to start with:
list_project_databases 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_project_databases call is checked against it from then on.
Questions about list_project_databases
Список managed-БД в указанном проекте. It is categorised as a Read tool in the Timeweb MCP Server, which means it retrieves data without modifying state.
list_project_databases accepts 1 parameter: project_id. Required: project_id. The full parameter table on this page comes from the server's own tool schema.
Register the Timeweb MCP server in PolicyLayer and add a rule for list_project_databases: 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_project_databases 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_project_databases 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_project_databases. 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_project_databases 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