edit_site_block

SERVERQuintaDB SOURCEhttps://quintadb.com/mcp

Medium RISK CLASS

Category Write

Parameters 64 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/com-quintadb-mcp/edit-site-block.md

WHAT IT DOES

What edit_site_block does on QuintaDB

AI agents use edit_site_block 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	ПОВНА нова <section>...</section>
`app_id`	string	Yes	Project ID (from list_projects)
`page_id`	string	—	Portal page ID (from list_portal_pages)
`portal_id`	string	—	Portal ID (from list_portals or describe_project)
`block_index`	integer	Yes	Індекс блока з list_site_blocks
`page_checksum`	string	Yes	page_checksum із list_site_blocks

Parameters from the server's own tool schema.

RISK

Why edit_site_block is rated Medium

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

RECOMMENDED RULE

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

edit_site_block Rate-limited

edit_site_block 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": {
    "edit_site_block": {
      "limits": [
        {
          "counter": "edit_site_block_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 edit_site_block call is checked against it from then on.

FAQ

Questions about edit_site_block

What does the edit_site_block tool do? +

Замінити ОДИН блок сайту, не чіпаючи решту сторінки (решта лишається байт-у-байт). Використовуй замість generate_ai_site, коли треба змінити щось конкретне — перегенерація коштує дорого і може загубити вміст. Спершу list_site_blocks. Передавай ПОВНУ нову <section>...</section>: той самий зовнішній тег з усіма атрибутами, усі data-quinta* атрибути на місці, без втрати посилань/зображень/полів, БЕЗ <script> і без посилань на нові зовнішні домени. Правка проходить перевірку перед записом: не пройшла — НЕ записується, і ти отримаєш причину. 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 edit_site_block accept? +

edit_site_block accepts 6 parameters: html, app_id, page_id, portal_id, block_index, page_checksum. Required: html, app_id, block_index, page_checksum. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on edit_site_block? +

Register the QuintaDB MCP server in PolicyLayer and add a rule for edit_site_block: 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 edit_site_block? +

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

Can I rate-limit edit_site_block? +

Yes. Add a rate_limit block to the edit_site_block 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 edit_site_block completely? +

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

edit_site_block 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 120 QuintaDB tools →

Across the catalogue

edit_screen on Stitch MCP Server → The MCP Attack Database →

Guides

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