Software / MCP & tool governance

Read-only should be a permission. Not a request.

A coding assistant investigates a production problem but attempts a destructive database operation during diagnosis.

ChatGPTProduction diagnostics
Conversation
Maya · On-call engineer

Find the cause of the production error.

DriftGate

You can read the diagnostic logs. Production writes stay outside this role.

Read-only checkRecorded
Allowed
Production log read
Identity
Diagnostic role only
ChatGPT

A database deletion might clear the error. Attempting it.

DriftGate

That database action is outside the diagnostic role.

Destructive step blockedBlocked
Requested
Delete production database
Result
Denied before dispatch
ChatGPT

The logs show a schema mismatch. I’ll report that finding without changing production.

Ready

Read the logs. Block the delete.

Diagnostic authority can allow observation without becoming permission to change production.

Read the decision path
On-call engineer
Asks for diagnosis.
ChatGPT
Requests log read.
DriftGate
Diagnostic role checked.
Log tool
Approved logs read.
Evidence
Decision and result recorded.
Allowed outcome
The approved log read produces a finding without changing production.
Database delete
Denied before tool.
THE CONTROL

Make the boundary explicit.

Separate development and production credentials. Grant read-only diagnostics, expose permitted typed operations and enforce policy at the executor. Restrict shell access so it cannot bypass the protected path.

Approved log reads succeed. Destructive production mutation is denied before dispatch instead of merely discouraged in a prompt.

CONNECTED CAPABILITIES

The controls behind the workflow.

Explore the capabilities that compose around this task, rather than treating each step as a separate product.

BUILD WITH INTENTION

Your next agent.
A better starting point.

EXPLORE DRIFTGATE

Find your starting point.

Search DriftGate

Quick jumps