Solutions · Legal

Control where your agents share privileged files.

Give your agents access to privileged files for research and drafting. Set policies that allow updates to the matter team’s page and block writes to client-shared pages after those files are read.

Request a demo See how to set up policies
Custom MCP
Reads a privileged case fileDocument management MCP · privileged read
✓ Allow
Notion
Publishes the summary to a client-shared pageNotion MCP · shared page
✗ Deny
Notion
Publishes it to the matter’s internal pageNotion MCP · internal page
✓ Allow

Why: privileged case file read by the same identity.

Both servers connect through Wicket.

Choose which sharing attempts to block.

Use these policies to let your agents read the records they need while blocking their writes to the destinations below.

  • Client updates

    A research agent reads a privileged case file, then tries to publish its summary to a page shared with the client.

    Custom MCP
    Reads a privileged case fileDocument management MCP · privileged read
    ✓ Allow
    Notion
    Publishes to a client-shared pageNotion MCP · shared page
    ✗ Deny

    PolicyBlock writes to pages shared with clients after the same identity reads privileged files.

  • Deal rooms

    A drafting agent reads a confidential deal memo in Confluence, then tries to post a summary to a Slack channel shared with the other side.

    Confluence
    Reads a confidential deal memoConfluence MCP · confidential space
    ✓ Allow
    Slack
    Posts to a shared external channelSlack MCP · external members
    ✗ Deny

    PolicyBlock posts to channels with external members after the same identity reads confidential data.

  • Discovery vendors

    A review agent reads privileged documents for a production set, then tries to copy them into a vendor’s Airtable base.

    Custom MCP
    Reads privileged documentsDocument management MCP · privileged read
    ✓ Allow
    Airtable
    Copies into a vendor’s baseAirtable MCP · external base
    ✗ Deny

    PolicyBlock writes to external bases after the same identity reads privileged documents.

Set sharing rules for each matter.

Let your agents research and draft with privileged files, then restrict sharing outside your matter team. Test your draft policy against the last 24 hours of calls before enforcing it.

  1. 01

    Connect the document system

    Run your document management system’s MCP server behind Wicket, with Confluence, Notion, Slack, and Airtable.

  2. 02

    Choose the matters to protect

    Scope your read policy to privileged matters and confidential deal spaces. Leave public filings outside that policy.

  3. 03

    Restrict client and counterparty sharing

    After an identity reads privileged files, block its writes to pages shared with clients and posts to Slack channels with external members.

  4. 04

    Block vendor uploads

    Block writes to vendor and external bases after the same identity reads privileged documents.

See which attempts to share were blocked.

Each denial records the agent, the attorney it acted for, the earlier privileged read, and the rule that applied. Your general counsel can see the attempted action and why it was blocked.

AUDIT-B35D0F4 ✗ Denied
Who
research-agent · OBO m.okafor@firm.example
What
notion.create_page → client-shared page
When
16:05:52 UTC · Notion MCP
After
dms.get_document · privileged case file · 16:03:11 UTC
Why
block-shared-after-privileged-read — privileged read matched earlier for this identity

Other solutions

Tell us what your agents need to access.

Request a demo Email eng@wicket.sh

Wicket applies policies using earlier policy matches for the same identity. It does not classify message contents, and both MCP servers must connect through Wicket. We’ll help you plan custom MCP connections during onboarding.