Fetch authenticated user profile from AWS API using the user\
AI agents call get-user-profile to retrieve information from Medicine Carousel 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 user profile information from AWS API after OAuth 2.1 authentication. It has no side effects—it queries and returns data without creating, modifying, deleting, or executing operations. The authentication requirement mitigates exposure.
From the tool's definition Tool name 'get-user-profile' and description 'Fetch authenticated user profile' indicate data retrieval with no modification or deletion. The verb 'Fetch' is a classic read operation.
Attacks that exploit this kind of access
Fetch authenticated user profile from AWS API using the user\. It is categorised as a Read tool in the Medicine Carousel MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Medicine Carousel MCP Server MCP server in PolicyLayer and add a rule for get-user-profile: 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 Medicine Carousel MCP Server. Nothing to install.
get-user-profile 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 get-user-profile 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 get-user-profile. 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.
get-user-profile is provided by the Medicine Carousel MCP Server MCP server (sudheerarava222/appsdk-mcp). 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 →