get_portal_page
Отримати HTML вмісту сторінки порталу. Якщо page_id не передано, використовується дефолтна сторінка порталу; якщо її неможливо однозначно визначити — спочатку виклич list_portal_pages. HTML обрізається щоб не перевантажити контекст.
This record as markdown: /tools/com-quintadb-mcp/get-portal-page.md
What get_portal_page does on QuintaDB
AI agents call get_portal_page 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) |
page_id | string | — | ID сторінки з list_portal_pages |
portal_id | string | Yes | Portal ID (from list_portals or describe_project) |
Parameters from the server's own tool schema.
Why get_portal_page is rated Low
This tool retrieves and queries portal page HTML content. It performs a read-only operation with no state changes, data modification, or external command execution. The mention of HTML truncation to avoid context overload further confirms it is purely retrieving and presenting existing data. Severity is low because reading portal page HTML has minimal blast radius even if misused by an agent.
From the tool's definition Tool description states 'Отримати HTML вмісту сторінки порталу' (retrieve HTML content of portal page). The verb 'get' and 'retrieve' indicate data fetching with no side effects. No modification, deletion, or execution capabilities are described.
Attacks that exploit this kind of access
The rule that runs get_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 get_portal_page, this is the rule to start with:
get_portal_page 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_portal_page call is checked against it from then on.
Questions about get_portal_page
Отримати HTML вмісту сторінки порталу. Якщо page_id не передано, використовується дефолтна сторінка порталу; якщо її неможливо однозначно визначити — спочатку виклич list_portal_pages. HTML обрізається щоб не перевантажити контекст. It is categorised as a Read tool in the QuintaDB MCP Server, which means it retrieves data without modifying state.
get_portal_page accepts 3 parameters: app_id, page_id, portal_id. Required: app_id, portal_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_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.
get_portal_page 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_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 get_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.
get_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