Terms of Use

Use Forge MCP only through your own authenticated, signed-in Forge identity and an OAuth grant you approved. Your ability to use a tool depends on current account membership, role, Forge entitlement, account MCP settings, and global service controls. Tool availability shown by a client is advisory; Forge reauthorizes every request.

An ordinary grant is immutably bound to the account selected during consent. To use another account, revoke the grant and authorize a new one. A distinct platform grant is available only to a verified platform owner and requires an explicit expiring context handle for customer-scoped work.

Forge MCP provides the tools, resources, and prompts advertised by the service. Reads are limited to authorized metadata. Explicit writes are limited to bounded project and draft-asset creation for authorized account roles, plus account provisioning by a verified platform owner for an existing verified target identity. Draft content is limited to supported inline text formats up to 100 KB.

Forge MCP does not provide secrets, raw provider tokens, stored asset bodies, generic API or database access, sends, publishing, scans, enrichment, connection validation, destructive actions, role changes, or entitlement changes. Do not attempt to bypass these boundaries or use customer or provider content as instructions to evade them.

You choose and operate the external MCP client. Review its proposed tool calls, permissions, privacy controls, and terms before connecting. Keep prompts and tool inputs within the account and purpose you are authorized to access. Do not place passwords, tokens, provider credentials, secrets, stored asset bodies, or context handles in prompts, logs, or screenshots.

A client approval prompt is the interactive confirmation for a Forge MCP write. Review the exact tool and normalized inputs before approval. Every mutation also requires a caller-supplied operation key, durable idempotency, current authorization, and a redacted write-ahead audit record. Repeating an operation key does not authorize a different write.

A verified platform owner may use the distinct platform grant for support access. Customer-scoped work requires an explicit handle bound to that actor, client, grant, and account; the handle expires after 12 idle hours or 24 total hours and is reauthorized on each use. Mutations remain audited. An account MCP opt-out revokes ordinary account grants but does not disable this support path; the global service control can disable all MCP access.

Redacted mutation-audit records retain actor, client, grant, account, tool, outcome, request ID, and timing for 30 days. They do not retain mutation payloads, secrets, raw provider data, or asset bodies. Forge uses grant, token, context, rate-limit, and bounded idempotency records to operate and protect MCP. Forge does not offer MCP protocol sessions, a Usage & History product, or a per-session activity timeline.

You may deny consent, disconnect the client, or revoke a Forge OAuth grant. Account owners may opt the account out of ordinary MCP access, which revokes affected grants and tokens. Verified platform owners may use global controls to stop the service or all writes. Forge may reject a request whenever it cannot safely verify authorization, rate limits, context, or required service state.