list_forms
Показати всі форми (таблиці) в проєкті. List all forms, tables, entities in a project.
This record as markdown: /tools/com-quintadb-mcp/list-forms.md
What list_forms does on QuintaDB
AI agents call list_forms 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 |
|---|---|---|---|
app_id | string | Yes | ID проєкту з list_projects |
Parameters from the server's own tool schema.
Why list_forms is rated Low
This tool retrieves and displays metadata about forms/tables/entities without creating, modifying, or deleting any data. It is a non-destructive query operation with minimal risk if misused by an agent, as it only exposes structural information about the database.
From the tool's definition Tool description explicitly states 'List all forms, tables, entities in a project' — a read-only enumeration with no modification or deletion capability.
Attacks that exploit this kind of access
The rule that runs list_forms 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_forms, this is the rule to start with:
list_forms 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_forms call is checked against it from then on.
Questions about list_forms
Показати всі форми (таблиці) в проєкті. List all forms, tables, entities in a project. It is categorised as a Read tool in the QuintaDB MCP Server, which means it retrieves data without modifying state.
list_forms accepts 1 parameter: app_id. Required: app_id. 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_forms: 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_forms 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_forms 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_forms. 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_forms 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