list_projects
Показати всі проєкти (бази даних) в QuintaDB акаунті
This record as markdown: /tools/com-quintadb-mcp/list-projects.md
What list_projects does on QuintaDB
AI agents call list_projects to retrieve information from QuintaDB 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 |
|---|---|---|---|
page | number | — | Сторінка (по 20 проєктів) |
Parameters from the server's own tool schema.
Why list_projects is rated Low
This is a data retrieval operation that lists existing projects without creating, modifying, deleting, or executing anything. It has minimal security impact—the main risk would be information disclosure if an agent lists projects it shouldn't have access to, but the tool itself performs only a read operation.
From the tool's definition Tool name 'list_projects' and description 'Показати всі проєкти (бази даних) в QuintaDB акаунті' (Show all projects/databases in QuintaDB account) indicate retrieval of project/database metadata with no modification or side effects.
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 QuintaDB, 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 QuintaDB, apply this rule, and every list_projects call is checked against it from then on.
Questions about list_projects
Показати всі проєкти (бази даних) в QuintaDB акаунті. It is categorised as a Read tool in the QuintaDB MCP Server, which means it retrieves data without modifying state.
list_projects accepts 1 parameter: page. The full parameter table on this page comes from the server's own tool schema.
Register the QuintaDB 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 QuintaDB. 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 QuintaDB MCP server (https://quintadb.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on QuintaDB, and thousands of servers like it.
This server
Across the catalogue