Grid82
grid82.comJoin the waitlist
DevelopersSafety and undo

Agent safety and undo

How external MCP clients execute writes compared to Grid82's built-in assistant, confirmation guards, and rolling back agent changes.

External MCP agents vs the built-in assistant

External MCP client or CLIGrid82 built-in assistant
Execution modelExecutes writes directly as you (prompting depends on your client’s approvals)Generates a proposal card; nothing mutates until you click Apply
PermissionsYour user roles, narrowed by approved OAuth apps and scopesYour user roles inside that UI plane
Attribution in LogStamped with your user ID and the MCP/CLI surfaceStamped with your user ID and the assistant surface

Because every external MCP connection acts strictly as you, an agent can never access a table or field hidden from your roles or escalate its own privileges.

Built-in safety guardrails

  • Confirmation on destructive targets. Deleting an organisation, suite, app, table, or field requires passing its exact current name in ?confirm=..., preventing accidental loops over empty or wrong IDs.
  • Schema impact guard. Dropping a table or field returns a list of affected views, formulas, permissions, and Interface pages until acknowledge=true is explicitly sent.
  • Scoped suite consent. On the OAuth consent page, tick only the specific apps an agent needs for its task. Membership checks run on every request, so removing someone from an app revokes agent reach immediately.
  • Atomic changesets. A batch insert of 500 records or a bulk sql.execute statement lands as one changeset in the app’s log. Revert any agent write cleanly using Log in the Studio, My recent changes in Runtime, or changesets.undo.
  • Read-only setup verification. The /agent-setup.md prompt explicitly instructs agents to test connections solely via read-only apps_list and me_get calls.

Use these docs with your AI tools

An AI agent can read this documentation directly. You do not need an account or an API key. Everything here is public and read-only.

Query these docs via MCP

Recommended

Add this server to Claude, Claude Code, Cursor, Mistral, or any tool that supports MCP. Your agent can then search Grid82 documentation and read it in full, instead of answering from memory.

https://grid82.com/docs/mcp
  • searchFind the passages that answer a question.
  • fetchRead one page in full, as Markdown.
  • list_pagesSee every page in this documentation.

Query these docs over HTTP

The same tools also work as plain web requests. Use this for scripts, or for any tool that does not support MCP. There is one endpoint per tool. Arguments go in the query string, and the answer comes back as JSON.

https://grid82.com/docs/api/docs/search?query=custom+domain

Read the OpenAPI description. It is built from the same definitions as the tools, so it always matches what the endpoints do.

Read these docs as Markdown

Add .md to any page URL to get its Markdown source. You can also send the headerAccept: text/markdown to the page URL itself.

To read the whole documentation in one file, open llms-full.txt. For a short index of every page, open llms.txt.