create_portal_page
Add a page of its own to a portal: a name and the page's content as HTML. It goes into the portal's menu under its name by itself — do not call add_portal_menu_item for it. For a page that shows the project's forms or tables use generate_ai_site instead.
This record as markdown: /tools/com-quintadb-mcp/create-portal-page.md
What create_portal_page does on QuintaDB
AI agents use create_portal_page to create or update resources in QuintaDB, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your QuintaDB environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
html | string | Yes | The page's content: headings, paragraphs, lists (or a whole HTML document) |
name | string | Yes | Display name |
app_id | string | Yes | Project ID (from list_projects) |
portal_id | string | — | From list_portals; may be left out when the project has one portal |
add_to_menu | boolean | — | false = create it without a menu item (default true) |
Parameters from the server's own tool schema.
Why create_portal_page is rated Medium
An AI agent can call create_portal_page faster than any human can review: one bad instruction and it creates or modifies resources in QuintaDB by the hundred, each call as confident as the last.
Risk signalsAccepts raw HTML/template content (html)
Attacks that exploit this kind of access
The rule that runs create_portal_page 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 create_portal_page, this is the rule to start with:
create_portal_page stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. 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 create_portal_page call is checked against it from then on.
Questions about create_portal_page
Add a page of its own to a portal: a name and the page's content as HTML. It goes into the portal's menu under its name by itself — do not call add_portal_menu_item for it. For a page that shows the project's forms or tables use generate_ai_site instead. It is categorised as a Write tool in the QuintaDB MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
create_portal_page accepts 5 parameters: html, name, app_id, portal_id, add_to_menu. Required: html, name, 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 create_portal_page: 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.
create_portal_page is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the create_portal_page 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 create_portal_page. 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.
create_portal_page 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