Sign out of this page ends your browser session on the MCP permission portal. It is not the same action as revoking an assistant’s existing connection.
To stop a connection, open Permissions, identify the assistant and company, and choose Revoke access. The portal explains that revocation takes effect on the connection’s next request.
Ordinary dashboard sign-out or browser-session expiry also should not be treated as a substitute for deliberate connection revocation. The explicit sign-out-everywhere action has broader session effects and can revoke MCP access as well.
Check the connection’s displayed state after changing it. Revocation stops future authorized requests; it does not erase records or documents already created through earlier valid operations. If you are offboarding an integration, review its existing work and any separate provider connections as needed. Use the specific connection control rather than assuming that closing a browser tab removes the assistant’s permission to act.
Was this article helpful?
Tell us whether this answered the question you came with.