Copilot Studio MCP and Dome
Build agents in Copilot Studio, and decide what they call. Copilot Studio connects agents to MCP servers by URL, with an API key in a header. Add a Dome Gateway that way and the agent reaches only the tools its rules allow. Every call lands in Dome's audit trail.
Dome governs every tool and model callin Microsoft Copilot Studio.
A URL and a header
The onboarding wizard takes the Gateway's MCP URL and an API key sent in the Authorization header. The key is a Dome agent key.
Tools named, not inherited
Rules list the tools each Copilot Studio agent may call, and anything else on the Gateway is refused.
Tool calls governed, models not
Copilot Studio runs its own models, and their calls don't pass through Dome, but every tool call does.
Copilot Studio on a Gatewayin three steps.
Register an agent in Dome, then add the Gateway in Copilot Studio's MCP onboarding wizard with the agent's key. The Dome commands were run against a workspace; the Copilot Studio steps come from Microsoft's docs.
Register an agent and issue its key
One Dome agent for each Copilot Studio agent you want to tell apart.
shelldome agents register --name helpdesk-copilot --gateway prod-gatewaydome agents create-key helpdesk-copilot --name copilot-studiodome rules apply helpdesk-copilot.cedar --agent helpdesk-copilot --name jira-helpdeskCopy the Gateway's MCP URL
It's endpoints.mcp_url in the output. Copilot Studio supports the Streamable HTTP transport, and so does the Gateway.
shelldome gateways get prod-gateway --jsonAdd the Gateway in Copilot Studio
On the agent's Tools page, choose Add a tool, New tool, then Model Context Protocol. Enter the URL, pick API key, type Header, header name Authorization. When you create the connection, enter Bearer followed by the agent key.
File tickets,read the knowledge base.
The permit lets the agent discover tools and call Atlassian. The forbid refuses every Atlassian tool except four: search, read and create Jira issues, and read Confluence.
cedar
permit (principal, action == Dome::Action::"mcp:discover", resource);
permit (principal, action == Dome::Action::"mcp:call", resource is Dome::MCPTool)when { resource.connection_name == "atlassian" };
forbid (principal, action == Dome::Action::"mcp:call", resource is Dome::MCPTool)when { resource.connection_name == "atlassian" }unless { ["searchJiraIssuesUsingJql", "getJiraIssue", "createJiraIssue", "getConfluenceContent"] .contains(resource.tool_name)};One call,two outcomes.
Switch the caller or the argument and watch the same call decide differently, with every decision landing in audit.
Call
agent helpdesk-copilot · scheduled
atlassian/createJiraIssue(cloudId: "7f6c3e2a-1d4b-4c8e-9a0f-2b5d8e1c4a9f")
- Agenthelpdesk-copilot is registered and active
- KeyBearer key from the Copilot Studio connection is valid
- RulecreateJiraIssue is on the list
DecisionAllowed
Bringing it alltogether.
Connecting Microsoft Copilot Studio to registered agents, tools, and identity in Dome completes a governed agent application.
Acting for
Agent
Microsoft Copilot StudioRuntime
Claude CodeClientControl point
GatewayEvery call decided and audited
RulesGuardsQuotas
Tools
Models
Common questionsabout Microsoft Copilot Studio.
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.
MCP server
GitHub
The GitHub MCP server behind the Tool Gateway, with rules that decide each call on its owner and repository.
Identity
Okta
Okta tokens verified on every agent call, so rules and audit name the person each agent acted for.
Client
Codex
Codex 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.
Agent frameworks and runtimes: govern agents without a rewrite
Build agents on the framework you already use. Dome governs their tool and model calls without a rewrite.