Documentation on AgentCore Identity for secure agent authentication and authorization.
AI agents call agentcore_identity to retrieve information from AWS AgentCore MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and queries documentation about identity management. It does not authenticate users, create identity policies, modify permissions, delete credentials, or execute authorization checks—it only provides reference material.
From the tool's definition Tool provides 'documentation on AgentCore Identity' with no indication of executing authentication/authorization actions, creating/modifying identity configurations, or deleting access controls. It is purely informational.
Attacks that exploit this kind of access
Documentation on AgentCore Identity for secure agent authentication and authorization. It is categorised as a Read tool in the AWS AgentCore MCP Server MCP Server, which means it retrieves data without modifying state.
Register the AWS AgentCore MCP Server MCP server in PolicyLayer and add a rule for agentcore_identity: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches AWS AgentCore MCP Server. Nothing to install.
agentcore_identity is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the agentcore_identity rule in your PolicyLayer policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.
Set action: deny in the PolicyLayer policy for agentcore_identity. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.
agentcore_identity is provided by the AWS AgentCore MCP Server MCP server (weiwarren/agentcore-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →