get_public_page
A table's PUBLIC page — the address its owner gives to people who have no account. Answers every switch of the page with its meaning, what a visitor can do there right now in plain words, and the addresses to hand out: the page's link, short link and embed code, and the same three for the public ...
This record as markdown: /tools/com-quintadb-mcp/get-public-page.md
What get_public_page does on QuintaDB
AI agents call get_public_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) |
entity_id | string | Yes | The table |
Parameters from the server's own tool schema.
Why get_public_page is rated Low
Even though get_public_page only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
The rule that runs get_public_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_public_page, this is the rule to start with:
get_public_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_public_page call is checked against it from then on.
Questions about get_public_page
A table's PUBLIC page — the address its owner gives to people who have no account. Answers every switch of the page with its meaning, what a visitor can do there right now in plain words, and the addresses to hand out: the page's link, short link and embed code, and the same three for the public FORM that adds a record. Call it when the person asks for a link to share, an embed code for their site, or whether their data is open. It is categorised as a Read tool in the QuintaDB MCP Server, which means it retrieves data without modifying state.
get_public_page 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_public_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_public_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_public_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_public_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_public_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