get_form_settings
Отримати детальні налаштування форми: post_action, sort_by, per_page, allow_delete, send_emails, inline_editing тощо.
This record as markdown: /tools/com-quintadb-mcp/get-form-settings.md
What get_form_settings does on QuintaDB
AI agents call get_form_settings 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 | Project ID (from list_projects) |
entity_id | string | Yes | Form ID (from list_forms or describe_project) |
Parameters from the server's own tool schema.
Why get_form_settings is rated Low
This tool retrieves form configuration metadata without creating, modifying, deleting, or executing any operations. It is a simple data retrieval endpoint that poses minimal risk if accessed by an AI agent, as it only exposes non-sensitive structural settings about form behavior.
From the tool's definition Tool name 'get_form_settings' and description explicitly state retrieval of configuration details (post_action, sort_by, per_page, allow_delete, send_emails, inline_editing). The verb 'Отримати' (retrieve/get) indicates a read-only query with no modification.
Attacks that exploit this kind of access
The rule that runs get_form_settings 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 get_form_settings, this is the rule to start with:
get_form_settings 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 get_form_settings call is checked against it from then on.
Questions about get_form_settings
Отримати детальні налаштування форми: post_action, sort_by, per_page, allow_delete, send_emails, inline_editing тощо. It is categorised as a Read tool in the QuintaDB MCP Server, which means it retrieves data without modifying state.
get_form_settings accepts 2 parameters: app_id, entity_id. Required: app_id, entity_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 get_form_settings: 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.
get_form_settings 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 get_form_settings 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 get_form_settings. 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.
get_form_settings 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