Amazon Bedrock AgentCore and Dome

1. 01

   Register an agent and issue its key

   One Dome agent stands for the AgentCore gateway, with the rule below applied to it.

   $ dome agents register --name agentcore-eng --gateway prod-gateway
   $ dome agents create-key agentcore-eng --name agentcore
   $ dome rules apply agentcore-eng.cedar --agent agentcore-eng --name github-read-only

2. 02

   Store the key in AgentCore Identity

   An API key credential provider holds the Dome key for outbound calls.

   $ aws bedrock-agentcore-control create-api-key-credential-provider \
     --name dome-agentcore-eng \
     --api-key "$DOME_AGENT_KEY"

3. 03

   Add the Dome Gateway as a target

   AgentCore sends the key as a Bearer token and lists the tools when the target is created.

   $ aws 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"}}}]'

Commands and rules tested against a Dome workspace on October 1, 2026. For anything about Amazon Bedrock AgentCore itself, see AWS's documentation.

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)
};