New: Automated Design is live

MCP Security

Secure AI Access to Your Wells

AI tools sign in as your engineers, see only what you approve, and leave a record of every call.

Access The Basics

Your Rules Still Apply

An AI tool gets the access your team approves, and nothing more.

Sign in as Yourself

Each engineer approves the connection with their own PetroBench account.

Approve the Permissions

Read, run or change: the tool only gets the scopes you tick, inside your role.

Keep a Record

Every call is logged with the user, the token and the tool.

Built on the PetroBench Platform

Open the Trust Center
  • SSO and SCIM
  • Role-based access
  • MFA
  • AES-256 at rest
  • TLS 1.2 and later

Questions From IT

Short answers for security reviews.

No. Your PetroBench account team turns it on when your organization asks.

Disconnect it under Settings > Connected Apps to end its access.

It sees what the signed-in person can see in their organization. Other organizations' data is never in scope.

Only with a write scope that the person approved. Keep write scopes to the people who need them, and review a change before you confirm it.

Yes. The MCP server takes the same tokens as the REST API, and service tokens support IP allowlists.

More questions? Contact Us

Run This on Your Own Wells

Your PetroBench account team turns on MCP access for your organization. Then ask your first question in plain words.