Agent inventory and identity

Register an agent profile

Use the Agents view or operator CLI to describe an agent and the requests that should match it. Choose a principal, model prefix, or supported attribute selector. Labels such as source and actor help inventory but are not necessarily enforceable rule predicates.

kastra agent list
kastra agent get AGENT_SLUG

Replace the slug with an existing inventory entry.

Define tool scope

The operator CLI supports managed tool-scope rules:

kastra agent scope AGENT_SLUG --deny-tool TOOL_A,TOOL_B

This changes the active policy and requires review and administrative authority. Test on a non-production environment and inspect the generated rule. Use actual tool names from the integration.

Bind identity where required

An unbound caller-supplied principal is advisory. When budget or policy enforcement depends on identity, configure the supported credential binding and inspect the returned trust information. An inventory record does not attest the executable, establish a delegation chain, or prevent a caller from bypassing a cooperative integration.

Verify scope

Test a request that should match the agent and one that should not. Confirm tool scope, environment, matched rule, and identity trust in the resulting decisions. Agent registration alone does not connect a hook or reroute provider traffic.