Notion MCP server and Dome
Let agents edit the wiki, and decide what they can overwrite. One bad rewrite can wreck a wiki page. Connect Notion's hosted MCP server to Dome once, and each edit is checked on its page and its command, with the Notion access of the person the agent acts for.
Dome provides a tool gatewayand authorization for Notion.
Edits, not rewrites
The same tool is allowed for a targeted edit and refused for a full-page replace, because rules read the command of every update.
Their login, their pages
A teammate connects Notion the first time an agent works for them. The agent reaches the pages that teammate can, no further.
Protected pages
Rules read the page_id of every update, and the handbook stays read-only to agents.
Notion behind the Gatewayin three steps.
Add Notion's server, sync its tools while signed in, then protect the pages that matter. Dome handles the OAuth client registration.
Add the Notion MCP server
Credentials are per user, through OAuth. Each teammate consents on their first call.
shelldome tools add --name notion \ --url https://mcp.notion.com/mcp \ --auth-method oauth --credential-type per-user \ --oauth-authorize-url https://mcp.notion.com/authorize \ --oauth-token-url https://mcp.notion.com/token \ --oauth-registration-url https://mcp.notion.com/register \ --gateway ops-gatewaySync the catalog
Notion's tool list is fetched with your login, so connect Notion yourself before you sync. Otherwise agents hit “tool not available in this gateway”.
shelldome tools catalog sync notionApply the rules
Put the handbook's page_id in the rule, scope it to one agent, and simulate an update before you deploy.
shelldome rules apply notion-args.cedar \ --agent wiki-gardener --name notion-per-page
Targeted edits,handbook untouched.
With the permit in place, one forbid turns away replace_content on every page and the other turns away any update to the handbook.
cedar
permit (principal, action == Dome::Action::"mcp:call", resource is Dome::MCPTool)when { resource.connection_name == "notion" };
forbid (principal, action == Dome::Action::"mcp:call", resource is Dome::MCPTool)when { resource.connection_name == "notion" && resource.tool_name == "notion-update-page" && resource has arguments && resource.arguments has command && resource.arguments.command == "replace_content"};
forbid (principal, action == Dome::Action::"mcp:call", resource is Dome::MCPTool)when { resource.connection_name == "notion" && resource.tool_name == "notion-update-page" && resource has arguments && resource.arguments has page_id && resource.arguments.page_id == "1c9e5d2a7b3f4e8a9d0c6b1a2e3f4d5c"};One call,two outcomes.
Switch the caller or the argument and watch the same call decide differently, with every decision landing in audit.
Command
agent wiki-gardener · acting as p.novak
notion/notion-update-page(page_id: "2a7f0c4e9b1d4c3a8e5f6a7b8c9d0e1f", command: "update_content")
- Agentwiki-gardener is registered and active
- Callerp.novak verified through Google
- RuleTargeted edits to the wiki are allowed
DecisionAllowed
Three agentson Notion.
These come from our template library, and each one reads broadly and writes narrowly.
meeting-notes-filer
File meeting decisions
Reads each meeting's notes and files the decisions as a page in the team wiki.
wiki-gardener
Tend the wiki
Finds stale wiki pages and fixes them with targeted edits, and is refused on full-page rewrites and the handbook.
onboarding-guide
Answer new hires
Answers new hires from the handbook and comments where a page is out of date.
Bringing it alltogether.
Connecting Notion to registered agents, models, and identity in Dome completes a governed agent application.
Acting for
Agent
Control point
GatewayEvery call decided and audited
RulesGuardsQuotas
Tools
NotionMCP server
Models
Common questionsabout Notion.
More of whatDome works with.
Model
Claude Fable
Fable 5.1 from Anthropic and Amazon Bedrock in one failover pool, open to one group and capped by quota.
Provider
Anthropic
The Claude API behind the Model Broker: the key held in Dome, every call authorized, metered and audited.
Identity
Okta
Okta tokens verified on every agent call, so rules and audit name the person each agent acted for.
Runtime
LangGraph
LangGraph agents with their model calls on the Model Broker and their MCP tools on the Tool Gateway.
Client
Claude Code
Claude Code on a Dome Gateway with per-developer sign-in, rules on every tool call, and audit by name.
Agent service
TinyFish
TinyFish's web agents behind the Tool Gateway, with rules that decide each run on the site it targets.
Talk with ourFDE team.
Or start free, and register your first agent in minutes. Connect it through a gateway, give it rules, and see every call it makes in one audit trail.
Talk with our FDE team
Our engineers design, build and run governed agents for the part of your business you want to change. You see what they deliver.
MCP servers for AI agents: per-argument rules on every call
Put any remote MCP server behind the Tool Gateway. Agents reach it through one governed endpoint, and rules decide each call on its arguments.