Audit Retool operations
Connect Retool with the mcp:read scope and prepare a weekly audit of production-touching queries, failing workflows, and unannounced app changes.
The Retool operations audit template reads the named Retool apps with their queries, resources, and recent workflow runs, then reports which queries touch production resources, which workflows failed or slowed since the last run, and which apps changed without a release note, with the app, query, or run cited for every finding. It shares the evidence-first posture of the weekly security audit: surface newly introduced risk, cite it, and leave the change to a person.
Enable and connect Retool
An operator must enable MANAGED_MCP_RETOOL_ENABLED. Retool's server at
mcp.retool.com supports dynamic client registration, so no static client is
needed; connect the Retool card and authorize with your own Retool login. Work
on Repeat requests only mcp:read; Retool's write and admin scopes are
requested only by routines that explicitly require them, and none does today.
Access follows your Retool organization permissions.
Set the variable
| Key | Example | Why it is a variable |
|---|---|---|
appNames | Refund console, Ops dashboard | Which internal tools are critical differs per team; list them separated by commas. |
Reference it in the instructions as {{appNames}}.
Current beta boundary
Retool is connection-only until exact authenticated tool schemas are captured and reviewed, so the packaged routine ships as a preview. After review, the first manifest should stay read-only: app, resource, query, and workflow-run reads. Editing, publishing, running, and deleting apps, queries, workflows, and resources are mutations and must remain blocked or approval-gated.
Recovery
If authorization expires or is revoked, the connection moves to
reauthorization_required; reconnect the same card to update it in place.