Evidence for a specific decision
Does an agent identity authorise a tool action?
You are connecting an agent to a service. Recognising the workload answers who is calling. It leaves a separate question: may that workload perform this operation on this resource for this user? A valid identity alone cannot settle a purchase or tool-action decision.
The published answer
AWS documents workload identities for agents, including automatic creation with AgentCore Runtime or Gateway deployments and explicit creation for custom deployments. An identity can participate in access policies; its existence does not establish permission for every action or the end user’s intent.
This entry reviews AWS documentation. It describes the documented creation and policy role of a workload identity. It does not inspect your account, validate its policies or prove that an action is authorised. Custom deployments must be distinguished from identities created by Runtime or Gateway deployments.
What to check in your own case
- Identify the deployment that owns the workload identity and the credential provider it can access.
- Check the operation, target resource and delegated scopes against the user’s task.
- Retain implementation-specific permission and enforcement evidence separately from the documentation reference.
Sources and exclusions
Published evidence record · Reviewed 2026-10-07
Understanding agent identities in Amazon Bedrock AgentCore
- Not established: blanket tool permission.
- Not established: verified user intent.
- Not established: automatic identity creation for every custom deployment.
Save the evidence behind your review
A saved snapshot preserves the source reference and the boundary between identity and permission for a later review. It grants no additional credentials or authority.
The complete answer is free. A saved snapshot costs £5 plus applicable VAT; an unsigned Evidence Receipt costs £19 plus applicable VAT. Recurring retrieval is also available. Retain your private access key before paying.
Use this example in an agent or API integration
Connect to https://varexis.tech/mcp, call find_evidence_questions with the search below, then use the returned route ID with preview_evidence_answer. No key is needed for previews.
{
"query": "Does an agent identity authorise a tool action?"
}The equivalent REST preview is POST https://varexis.tech/api/index/preview with JSON:
{
"route_id": "agentic_reviewed_aws_agentcore_workload_identity"
}Actual published-snapshot excerpt; the full response also includes each public source record and its limitations:
{
"route_id": "agentic_reviewed_aws_agentcore_workload_identity",
"answer": "AWS documents workload identities for agents, including automatic creation with AgentCore Runtime or Gateway deployments and explicit creation for custom deployments. An identity can participate in access policies; its existence does not establish permission for every action or the end user’s intent.",
"snapshot_sha256": "b03518a770ba7939b76aa9105a1de2dd946ec88959d0ffb064e6ce3e0cb8e7fa",
"sources": [
{
"record_id": "VXI-EXT-AWS-AC-ID-01-v1",
"url": "https://varexis.tech/varexis-index/records/aws-agentcore-workload-identity.json",
"content_sha256": "4b471e827fb8c1961069f4f78f683a120d353bd7e30947e0dfff332613d92ef6"
}
]
}
