Seguridad

• Every request validates the OAuth JWT, issuer, audience, expiry and client ID.
• The active MCP grant must match the same user, client and workspace.
• Reads use the caller bearer token, preserving existing workspace and project RLS.
• Provider tokens, raw payloads, prompts, private paths and signed URLs are excluded.
• Audit rows contain sanitized identifiers, filters, outcomes and duration only.

Social tools return safe public account metadata and normalized analytics. OAuth tokens, provider account secrets and raw provider payloads never leave the backend.

Conversation writes append only to a user-owned thread. Generation uses prepare → confirm and idempotency. Generated content remains a draft; MCP does not publish it.