The safeguards map / 3.5 Policy engines
Amazon Bedrock AgentCore Policy
Drafted with AI
Drafted with AI from the cited sources under the direction of UnGovr staff. UnGovr holds editorial responsibility for this page. How this site is made
A managed policy engine that evaluates Cedar policies against each AgentCore Gateway tool call, using the caller identity and the tool input parameters.
Where it sits
3.5 Policy engines (primary): Evaluates each request that passes through an AgentCore Gateway against Cedar policies held in a policy engine, using user identity and tool input parameters, before tool access is allowed.
Policy in AgentCore intercepts all agent traffic through Amazon Bedrock AgentCore Gateways and evaluates each request against defined policies in the policy engine before allowing tool access.
captured
Policies are constructed using Cedar language
captured
Policy in AgentCore supports fine-grained permissions based on user identity and tool input parameters
captured
Facts
- Concern
- security
- Names the law
- no
- Subject
- agentAI system
- Used by
- those who run it
- Runs
- at runtime
- Policy comes from
- owner-entered settings
Handoffs
consumes Policy: Cedar policies
Every quote is verbatim from a stored capture of the page linked under it. Placement is our reading of the product's own documentation; no publisher has reviewed or endorsed it. Rows CC BY 4.0. Names, marks and logos belong to their owners; logos identify each product and are not part of the dataset.