update_public_page

SERVERQuintaDB SOURCEhttps://quintadb.com/mcp

Medium RISK CLASS

Category Write

Parameters 33 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/com-quintadb-mcp/update-public-page.md

WHAT IT DOES

What update_public_page does on QuintaDB

AI agents use update_public_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
`app_id`	string	Yes	Project ID (from list_projects)
`settings`	object	Yes	setting: true \| false. allow_database (the page shows the records), allow_search (a search box; with the records hidden — a search-only page that shows what was
`entity_id`	string	Yes	The table

Parameters from the server's own tool schema.

RISK

Why update_public_page is rated Medium

An AI agent can call update_public_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.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs update_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 update_public_page, this is the rule to start with:

update_public_page Rate-limited

update_public_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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "update_public_page": {
      "limits": [
        {
          "counter": "update_public_page_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect QuintaDB, apply this rule, and every update_public_page call is checked against it from then on.

FAQ

Questions about update_public_page

What does the update_public_page tool do? +

Change what a visitor with no account sees and may do on a table's public page. Pass only what the person asked for. The answer says CHANGED / UNCHANGED per setting and, in plain words, what anyone with the link can do now — tell the person that sentence when a switch opened their records. The page's login and password are never arguments: switching password_database_boolean on makes them when the page has none, and the answer carries a link to a page that shows them to the owner once. 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.

What parameters does update_public_page accept? +

update_public_page accepts 3 parameters: app_id, settings, entity_id. Required: app_id, settings, entity_id. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on update_public_page? +

Register the QuintaDB MCP server in PolicyLayer and add a rule for update_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.

What risk level is update_public_page? +

update_public_page is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit update_public_page? +

Yes. Add a rate_limit block to the update_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.

How do I block update_public_page completely? +

Set action: deny in the PolicyLayer policy for update_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.

What MCP server provides update_public_page? +

update_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.

KEEP EXPLORING

More on QuintaDB, and thousands of servers like it.

This server

All 150 QuintaDB tools →

Across the catalogue

aroflo_create_or_update_record on AroFlo MCP → The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →