Features: agent interface
Built for agents as well as people.
Anything the console does, an agent can do through a tool, and Renkara's agents do. The tools are not a second code path: they call the same handlers, so the same checks apply.
MCP
The surface
Foundry serves 153 tools at /mcp over streamable HTTP, built with FastMCP. Every tool name starts with foundry_. The mount refuses a call without a service token or an admin sign-in, because the tools can create and destroy infrastructure.
| Stacks and deployments | list, get, create, update, plan, apply, destroy, drift, versions, rollback |
|---|---|
| Resources and releases | add, update, validate, refresh, remove, resource types and schemas, release plan, approve, apply, rollback |
| Inventory and scans | query, summary, facets, scans, untagged, expiring, resource timeline |
| Compliance and advisor | packs, runs, findings, checks, savings |
| Cost and network | summary, forecast, anomalies, taxonomy, chargeback, CIDR and IP space |
| Governance and remediation | taxonomy, enforcement, remediation policies, approvals, sweep status |
| Synthesis, adoption, and continuity | synthesize, adopt, history, mirror, blast radius, access graph |
What a tool will not do
A standby copy of Foundry reads its own database and refuses every tool that would act on AWS. In production, Foundry never uses its own task credentials to act in an account: a tool call that reaches AWS without an account session fails instead of falling back.
Contact
Questions about this tool?
Write to Renkara Media Group and a person will answer.