Skip to content
AI Agent Access Control

Restrict which principals can invoke each tool endpoint

Check 20 of 30: Restrict which principals can invoke each tool endpoint. A tool endpoint that accepts calls from any caller can be used without the agent. Limiting invokers means only the intended agent can trigger the action. In AWS: Attach a resource-based policy on the tool's Lambda function that allows only the Bedrock service principal for one agent ARN.

The whole checklist ยท The map

Why it matters

A tool endpoint that accepts calls from any caller can be used without the agent. Limiting invokers means only the intended agent can trigger the action.

How, in each cloud

AWS
Attach a resource-based policy on the tool's Lambda function that allows only the Bedrock service principal for one agent ARN.
Google Cloud
Grant the Cloud Run Invoker role only to the agent's service account.
Azure
Assign Foundry roles at agent scope to grant endpoint access to one agent without granting it for all agents in the project.

What the documentation says

  • "Resource-based policy to allow Amazon Bedrock to invoke an action group Lambda function" (source)
  • "Cloud Run Service Invoker ( roles/run.servicesInvoker )" (source)
  • "so use this scope to grant access to a specific agent's endpoints without granting endpoint access to all agents in the project" (source)

Sources

  1. docs.aws.amazon.com/bedrock/latest/userguide/agents-permissions.html, read 10 Nov 2026
  2. cloud.google.com/run/docs/securing/managing-access, read 10 Nov 2026
  3. learn.microsoft.com/en-us/azure/ai-foundry/concepts/rbac-foundry, read 10 Nov 2026

Last reviewed 16 Nov 2026.