DPO Radio

Issuing MCP API Keys

Overview Image

Why MCP API Key Issuance Matters

A compliance team rolling out external AI integrations needs key issuance that holds up to operator turnover, suspected leaks, and audit scrutiny. Storing API keys in plaintext anywhere — repository, configuration file, password manager that the whole team can read — is the failure mode that ends compliance teams' inspection-readiness story.

The Forseti MCP issuance flow is built around three load-bearing rules. The plaintext key is shown exactly once at issuance and bcrypt-hashed at rest; the platform retains no recoverable plaintext. Each key carries its own tool whitelist that scopes which Forseti tools the key can call. Rotation has a 5-minute grace window so in-flight integrations finish without a hard cutover.

The issuance surface is permission-gated. Only administrators holding the MCP key permissions can issue, rotate, or revoke. Every issuance, rotation, and revocation is recorded in the audit trail with the operator and the time, so the inspection-readiness story is complete.

How It Works

Permission-Gated Issuance Surface

Administrators with the MCP key permissions open a dedicated MCP Keys page under Forseti. The page lists every active and historical key for the organisation with label, prefix, tool list, last-used timestamp, call count and status (active, revoked, or expired). Permissions are required to view, issue, rotate, or revoke.

Bcrypt-Hashed Storage With Plaintext Displayed Once

The platform generates the key at issuance, displays the plaintext exactly once in a modal, and stores only a bcrypt hash plus the first-eight-character prefix for inventory display. The plaintext is unrecoverable; if it is lost, the administrator rotates or revokes the key and issues a fresh one.

Per-Key Tool Whitelist

Each key carries its own tool whitelist that names which Forseti tools the key is permitted to call. The whitelist is the first gate at every call; tools outside the whitelist return a scope-mismatch error. Best practice is to issue each integration the smallest whitelist that covers its use case.

Optional Expiry and Status Callback

A key can carry an expiry date, after which it stops authenticating without anyone having to remember to revoke it. A key can also carry a status callback address: the outcome of each write it proposed is posted there, signed with a secret shown once, so an integration learns when its proposal was approved, declined or expired.

Rotation With a 5-Minute Grace Window

Rotation mints a fresh plaintext and keeps the old plaintext authenticating for 5 minutes so in-flight integrations finish without a hard cutover. After the grace window the old plaintext is hard-rejected. The administrator updates the external integration to the new plaintext during the grace window.

Immediate Revocation Without Grace

Revocation is immediate — the next call from the revoked key is rejected. There is no grace window for revocation because revocation is the response to a suspected leak. Revoked keys remain in the inventory list as revoked so audit reviewers can trace historical activity, but they cannot be re-activated.

The Difference

Graphic Image

Without Structured Key Issuance

Graphic Image

With Forseti MCP Key Issuance

IconAPI keys live in plaintext in configuration files, repositories, or shared password managers.
IconPlaintext is displayed exactly once at issuance and bcrypt-hashed at rest. The platform retains no recoverable plaintext.
IconCompromised keys cannot be revoked atomically; in-flight calls succeed against the rotated key.
IconRevocation is immediate. Rotation has a 5-minute grace window for clean cutover.
IconThere is no per-integration tool whitelist; one leaked key grants the full tool surface.
IconEach key carries its own tool whitelist. A leaked key cannot exceed the issuance-time scope.
IconIP-source restrictions either do not exist or are enforced inconsistently across integrations.
IconA key can expire on a date set at issuance, and stops authenticating when it does.
IconAudit trails carry no record of who issued, rotated, or revoked a key.
IconEvery issuance, rotation, and revocation is in the audit trail with operator and time.

Built for Auditable AI

Build For Image

The plaintext is bcrypt-hashed at rest. The platform retains no recoverable plaintext. Lost plaintext cannot be recovered; the response is rotate or revoke and re-issue.

Build For Image

Each key issuance is permission-gated and audit-trailed. The permission check resolves at issuance time; an administrator who loses MCP-key permissions cannot issue new keys after permission revocation.

Build For Image

The tool whitelist is the first gate at every call. Tools outside the whitelist return a scope-mismatch error before any handler runs. A compromised key cannot exceed the issuance-time scope, no matter the calling pattern.

Overview Image

Use the Right Connection for the Caller

Choose OAuth for a person connecting a supported client, so the connection uses that person's access. Reserve organisation-scoped API-key access for integrations that need it.

Background Image

See MCP Key Issuance in Action

Ready to see a key issued, its tool whitelist scoped, and the plaintext copied into a secret manager in under two minutes? Request a personalised demo.

Demo Image
Ronni K. Gothard Christiansen

Ronni K. Gothard Christiansen - Technical Privacy Engineer & CEO

Technical Compliance Expert, 32+ Years Open Source Advocate, X-BoD Open Source Matters Inc.

Or contact via

ronni@aesirx.io+84 909 500 760

Next Steps

Icon Image

Start a Compliance Pilot

Issue a read-only MCP key, scope it to a specific integration, and use the audit trail to verify which tools the integration is calling.

Icon Image

Discuss Your Compliance Needs

Talk to our team about how to scope keys for an Anthropic Console research surface versus a Claude Code drafting integration.

Frequently Asked Questions About MCP API Key Issuance

The plaintext is unrecoverable by design. The platform stores only the bcrypt hash. If the plaintext is lost the administrator rotates the key (which mints a fresh plaintext and keeps the old one authenticating for 5 minutes) or revokes the key and issues a new one.

Yes. Every key carries its own tool whitelist that names which Forseti tools the key may call. The whitelist is the first gate at every call. The recommended pattern is to issue each integration the smallest whitelist that covers its use case.

The 5-minute grace window lets in-flight integrations finish against the old plaintext while the administrator updates the external configuration to the new plaintext. After the grace window the old plaintext is hard-rejected. Revocation, by contrast, is immediate — no grace window.

No. A key carries no per-key address restriction. Limit what a key can reach with its tool list and an expiry date, keep it in a secret manager, and revoke it at once if it may have been exposed.

Only administrators holding the MCP key permissions. The permission check resolves at issuance time; an administrator who loses the permission cannot issue new keys after the permission is revoked. Every issuance, rotation, and revocation is recorded in the audit trail with operator and time.