Skip to main content
Glama
akeyless-community

akeyless-agentcore-rta

Official

akeyless-agentcore-rta

Akeyless Agentic Runtime Authority (ARA / RTA) for AWS Bedrock AgentCore.

Agents call list-secrets, query-db, service-execute, and list-sub-tools. Credentials stay on your Akeyless Gateway — tool responses contain paths, metadata, and query/action results only.

Not the secrets-fetch library. For get_secret() / pulling secret values into the agent, use akeyless-agentcore-runtime. You can use both in one architecture (bootstrap via secrets runtime; DB/cloud via this package).

Concern

This package (RTA)

Secrets runtime

Goal

Do work with secrets

Fetch secret values

Tools

list-secrets, query-db, service-execute, list-sub-tools

list / get secret

Credentials in agent

Never

Yes (values returned)

Gateway

Required customer GW with ARA

SaaS API or GW OK

Requirements

  • Python 3.10+

  • Akeyless Gateway with ARA enabled (not api.akeyless.io)

  • Auth method your AgentCore role can use (production: AWS IAM cloud identity)

Related MCP server: openserverless-mcp

Install (local)

cd bedrock-agentcore-akeyless-rta
python3 -m venv .venv
source .venv/bin/activate
pip install -e ".[mcp,dev]"

Quick start — client

from akeyless_agentcore_rta import AkeylessRtaClient

client = AkeylessRtaClient()  # reads AKEYLESS_* env
for s in client.list_secrets():
    print(s.name, s.target_type)  # never prints credentials

rows = client.query_db("SELECT 1", secret_name="/prod/db/readonly")
print(rows.results)

Quick start — MCP on AgentCore

# env (required)
export AKEYLESS_GATEWAY_URL=https://gw.example.com:8000
export AKEYLESS_ACCESS_ID=p-xxxxx
export AKEYLESS_ACCESS_TYPE=aws_iam   # or access_key locally

python examples/mcp-server/server.py
# AgentCore: protocol MCP → examples/mcp-server/server.py

Environment

Variable

Required

Notes

AKEYLESS_GATEWAY_URL

Yes

Customer GW (https://gw:8000 or …/api/v2). Public SaaS rejected.

AKEYLESS_ACCESS_ID

Yes*

Auth method access id

AKEYLESS_ACCESS_TYPE

No

Default aws_iam. Also: access_key, oidc, saml, jwt, …

AKEYLESS_ACCESS_KEY

For access_key

Local/dev only

(OIDC/SAML)

—

Browser login to Gateway; needs Access ID only

AKEYLESS_AGENT_ID

No

Default bedrock-agentcore

AKEYLESS_MCP_ID

No

Default akeyless-agentcore-rta

AKEYLESS_DEFAULT_SECRET_NAME

No

Optional default path for execute tools

* Or AKEYLESS_TOKEN for a pre-issued session token.

Docs

Guide

Description

Akeyless setup

Auth method, ARA RBAC, chicken-and-egg IAM bind

AgentCore deploy

MCP protocol, envVars, invoke

Security

Checklist

Maintainer guide

Branch protection, approvals, PyPI environment

Publishing to PyPI

Trusted publishing setup

Contributing

Development setup

Repository: github.com/akeyless-community/bedrock-agentcore-akeyless-rta

Development

pip install -e ".[mcp,dev]"
pytest

Run pytest inside this package directory so the workspace root does not collect unrelated tests.

Related MCP Connectors

Related MCP Servers

  • A
    license
    Not graded
    quality
    C
    maintenance
    Enables AI agents to securely discover, invoke, and manage tools through a hardened MCP endpoint with protections like injection detection, circuit breakers, retry backoff, response caching, context-window limiting, and state snapshots.
    15 npm
    MIT
  • A
    license
    Not graded
    quality
    B
    maintenance
    Enables agent clients to safely connect to tools and execution resources through MCP with authorization, approvals, audit, chat-context isolation, SSH/Docker access, and long-running command session tracking.
    MIT
  • F
    license
    Not graded
    quality
    A
    maintenance
    Enables organizations to govern agent tool access by onboarding remote MCP servers, defining function-level allow lists and credential modes, and exposing permitted tools through a single unified MCP endpoint with search and execute functions.
    -