Amazon Bedrock AgentCore and Dome
Run agents on AgentCore under the same rules as the rest of your estate. AgentCore Gateway takes any remote MCP server as a target, and a Dome Gateway is one. Dome then decides every tool call AgentCore agents make, under the same rules as your agents anywhere else. Agents on AgentCore Runtime run your own code, so they can call Dome directly too.
Dome governs every tool and model callin Amazon Bedrock AgentCore.
A target like any other
AgentCore Gateway adds the Dome Gateway by URL and syncs its tools. Its catalog holds only the tools the Dome agent is granted.
Rules that travel
The rule that refuses a merge on AgentCore refuses it on any other runtime, and audit puts every call in one trail.
Models from your own code
AgentCore Runtime hosts code you write, in any framework. Point its model client at the Broker and model calls are governed too.
AgentCore behind Domein three steps.
Register a Dome agent for the AgentCore gateway, store its key in AgentCore Identity, and add the Dome Gateway as an MCP server target. The Dome commands were run against a workspace; the AgentCore commands come from AWS's docs.
Register an agent and issue its key
One Dome agent stands for the AgentCore gateway, with the rule below applied to it.
shelldome agents register --name agentcore-eng --gateway prod-gatewaydome agents create-key agentcore-eng --name agentcoredome rules apply agentcore-eng.cedar --agent agentcore-eng --name github-read-onlyStore the key in AgentCore Identity
An API key credential provider holds the Dome key for outbound calls.
shellaws bedrock-agentcore-control create-api-key-credential-provider \ --name dome-agentcore-eng \ --api-key "$DOME_AGENT_KEY"Add the Dome Gateway as a target
AgentCore sends the key as a Bearer token and lists the tools when the target is created.
shellaws bedrock-agentcore-control create-gateway-target \ --gateway-identifier "$AGENTCORE_GATEWAY_ID" \ --name dome \ --target-configuration '{"mcp": {"mcpServer": { "endpoint": "https://<gateway-host>/gateways/<gateway-id>/mcp"}}}' \ --credential-provider-configurations '[{ "credentialProviderType": "API_KEY", "credentialProvider": {"apiKeyCredentialProvider": { "providerArn": "<credential-provider-arn>", "credentialLocation": "HEADER", "credentialParameterName": "Authorization", "credentialPrefix": "Bearer"}}}]'
Review code,never change it.
The permit lets the agent discover tools and call GitHub. The forbid refuses merges and every tool that writes to a repository.
cedar
permit (principal, action == Dome::Action::"mcp:discover", resource);
permit (principal, action == Dome::Action::"mcp:call", resource is Dome::MCPTool)when { resource.connection_name == "github" };
forbid (principal, action == Dome::Action::"mcp:call", resource is Dome::MCPTool)when { resource.connection_name == "github" && ["merge_pull_request", "push_files", "create_or_update_file"].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 agentcore-eng · scheduled
github/pull_request_read(owner: "acme", repo: "web", pullNumber: 482)
- Agentagentcore-eng is registered and active
- KeyBearer key from AgentCore Identity is valid
- RuleGitHub reads are allowed
DecisionAllowed
Bringing it alltogether.
Connecting Amazon Bedrock AgentCore to registered agents, tools, and models in Dome completes a governed agent application.
Acting for
Agent
Amazon Bedrock AgentCoreRuntime
LangGraphRuntimeControl point
GatewayEvery call decided and audited
RulesGuardsQuotas
Tools
Models
Common questionsabout Amazon Bedrock AgentCore.
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
Atlassian
The Atlassian Rovo MCP server behind the Tool Gateway, with rules that decide each Jira and Confluence call on its tool and site.
Identity
Okta
Okta tokens verified on every agent call, so rules and audit name the person each agent acted for.
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.
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.