Product
MCP ManagementHosted servers, scoped access, call logsAPI CatalogDiscover, organize, and score your APIsAPI TestingInspect quality and try your MCP toolsAPI ContractsChoose what each audience can access
How it worksPricingBlogDocsAbout SutraStart free
Sutra / SECURITY & ACCESS

SECURITY & ACCESS

Make access
a deliberate decision.

A useful integration needs clear boundaries. Here is how to think about workspace access, contracts, and upstream credentials in Sutra.

THE CONTROL POINTS

Review the whole path.

Your workspace, published interface, gateway, and upstream API each have a role.

01

Workspace access.

Use authenticated workspace access for private catalogs, contracts, and server configuration. Decide who should be allowed to manage the interface.

02

Published surface.

Select the endpoints and response fields intended for each audience. Review public artifacts and install pages as consumer-facing material.

03

Upstream authorization.

Your API remains responsible for authorization. Use appropriate credentials and verify that the upstream enforces the intended operation and data boundaries.

BEFORE YOU CONNECT

Small checks.
Important boundaries.

  1. Start with a sandbox and read-only tools.
  2. Review every endpoint in a published contract.
  3. Check fields for secrets and personal data.
  4. Verify visibility and authentication settings.
  5. Keep private credentials out of shared client examples.
  6. Inspect call history after your first integration.

A FEW DETAILS

Good questions.

Talk to us →
Is an API quality score a security certification?

No. Catalog scores evaluate specific properties of available API metadata. They do not certify your application, deployment, or compliance posture.

Can you review my organization’s requirements?

Yes. Contact us to discuss your deployment, retention, access, and procurement requirements. Confirm any specific assurance or contractual commitment directly with the team.

How do I report a security concern?

Email hello@getsutra.me with the subject “Security report”. Describe the affected component and a minimal reproduction without sending live secrets or sensitive customer data.