MCP connections: approved apps and accounts

Source: deck slide 9 · Connection controls | Risks #3, #4, #16, #21

Scope: MCP only. OAuth/API application and destination controls; confirm WPP configuration.

Legend: Today = Wrike capability | Confirm = setup/evidence. See the overview for all labels.

The deck gives this slide a single column, "Wrike MCP — control / owner". Two rows share the title "#4 MCP Security", so their headings below add the concern in the deck's wording.

#3 Permissions & Identity#

Unapproved applications gain access.

Wrike MCP — control / owner

• Today: An account-side allowlist limits which OAuth/API applications can access the WPP Wrike account.
• Confirm: Agree the approved client IDs and configure them with Support.

#4 MCP Security: integration connects to the wrong account#

An integration connects to the wrong account.

Wrike MCP — control / owner

• Today: An OAuth-client allowlist limits which Wrike account IDs the integration can connect to.
• Confirm: Set the approved corporate accounts and check the supported OAuth flow with Support.

#16 Cross-System Data Leakage · #21 External AI Platform#

Data crosses approved boundaries.

Wrike MCP — control / owner

• Note: Tracking cross-system data passage is out of Wrike MCP boundaries and should be governed on the LLM client / MCP gateway layer.

#4 MCP Security: previously issued tokens retain access#

Previously issued tokens retain access.

Wrike MCP — control / owner

• Note: Changing an allowlist does not guarantee that existing tokens stop working immediately. Confirm the separate revocation procedure before relying on a list change to remove access.

Related pages#

• Identity and permissions covers token issue, expiry, rotation and revocation (#4).
• Disablement and incident response covers who stops a connection and revokes tokens (#9).

Discussion log#