Restrict Space Access

Last modified by gabrielc on 2026/10/21 10:53

Steps

Narrow what this wiki's MCP tools may reach to a chosen set of spaces and documents. It narrows results on top of each user's own rights and is not an access-control boundary in itself (see MCP User Permissions).

  1. Open the wiki's administration and go to "Other > MCP Server".
  2. Expand "Additional filters" and set "Space Filter Mode" to whitelist to expose only what you list, or to blacklist to expose everything except what you list.

    The Space access part of the Additional filters group, with the Space Filter Mode select set to whitelist and highlighted

  3. Pick the spaces and documents in the tree below. A space entry covers its whole subtree; a document entry matches that one document. With cross-wiki reach on, an entry can name another wiki (second:Sandbox) and then matches content in that wiki only.

    The space picker of the MCP Server administration, with the Release Notes space ticked and highlighted, and the matching chip listed above the tree

  4. Save the configuration. The change applies to the next request, with no restart.
  5. Ask a connected agent to survey the wiki and check that it reports only what you allowed. A filtered document is refused with a message saying it is outside what the endpoint exposes, not as missing.

    A terminal session in which the assistant surveys the wiki and reports the single allowed space, highlighted

FAQ

Does the filter replace the rights check?

No. A document the filter allows must still pass the usual view or edit authorization, and a user still sees only what their own account may see. The refusal names the page, so the filter's entries are observable to the agent: it is scoping, not secrecy.

What happens if the configuration cannot be read?

The filter fails closed: the document is denied and searches return nothing, so a transient glitch cannot silently defeat a blacklist.

Does it cover semantic search?

No. The two collection tools are governed by collection access rights instead of by this filter.

Which wiki's filter applies when an endpoint reaches another wiki?

The endpoint's own. The target wiki's filter is never consulted. With cross-wiki reach on, an entry can be wiki-prefixed and then matches content in that wiki only.

What if the whitelist has no entries, or an entry is malformed?

A whitelist or blacklist with no spaces and no documents imposes no restriction at all, so an empty whitelist does not deny everything. A malformed entry is skipped with a WARN in the server log and matches nothing.

Related

Get Connected