describe_project
Повна схема проєкту: всі форми, поля з типами та варіантами вибору, кількість записів, портали. Викликай перед create_record або коли треба зрозуміти структуру бази даних.
This record as markdown: /tools/com-quintadb-mcp/describe-project.md
What describe_project does on QuintaDB
AI agents call describe_project 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 describe_project is rated Low
The tool retrieves metadata about project structure (forms, fields, record counts, portals) with no side effects. It is informational only, used to understand the database schema before performing other operations. This is a classic Read category tool — no data is modified, created, or deleted.
From the tool's definition The tool returns 'Повна схема проєкту' (full project schema), 'всі форми' (all forms), 'поля з типами' (fields with types), 'кількість записів' (number of records), 'портали' (portals).
Attacks that exploit this kind of access
The rule that runs describe_project 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 describe_project, this is the rule to start with:
describe_project 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 describe_project call is checked against it from then on.
Questions about describe_project
Повна схема проєкту: всі форми, поля з типами та варіантами вибору, кількість записів, портали. Викликай перед create_record або коли треба зрозуміти структуру бази даних. It is categorised as a Read tool in the QuintaDB MCP Server, which means it retrieves data without modifying state.
describe_project 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 describe_project: 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.
describe_project 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 describe_project 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 describe_project. 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.
describe_project 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