Revoked access must stop at the same boundary where connected table data is returned.
Enterprise administrators need immediate control, while approved MCP workflows depend on uninterrupted access to connected tables.
Who you’d be doing this for
“I removed their access this morning, and legal is asking why the table still came back through MCP.”
Antonella Gomes · Document Administrator
Manages access and governance for sensitive operational tables used through connected document workflows.
What is at stake
A revoked user can still receive rows through an MCP request after disappearing from the document. You must weigh immediate containment against a durable change to the shared query path.
Why it isn’t already fixed
Every obvious fix costs something else. That’s the part you’d have to decide.
- immediate containment vs approved workflow continuity
- fresh authorization checks vs query latency
- shared infrastructure change vs compliance deadline
- automated analysis vs verified security evidence
Why Superhuman
Superhuman Docs connects governed tables, role-based access, and MCP access in the same enterprise workspace.
Written with these in mind
Not your kind of problem? 30 more at Superhuman, or browse every organization.
This is the setup. The work is inside.
Running it puts you in the room: the full situation and its constraints, stakeholders who push back in their own words, and the decisions that are yours to make. What you produce becomes a Day One Plan — work you can show someone instead of describing.