AI agents call get_user_info to retrieve information from Hevy 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 data with no modification or side effects. While categorized as Read (lowest severity among functional categories), it is assessed at medium severity because user_id and profile information can be sensitive PII (personally identifiable information) that an unauthorized or misbehaving agent could exfiltrate or misuse for identity spoofing, account linkage across services, or social…
From the tool's definition Tool description explicitly states it 'Get[s] the authenticated user's profile info' including user_id, name, and profile_url. The verb 'get' and the read-only nature of retrieving profile information confirm this is a Read operation.
Attacks that exploit this kind of access
Get the authenticated user's profile info (user_id, name, profile_url). It is categorised as a Read tool in the Hevy MCP Server, which means it retrieves data without modifying state.
Register the Hevy MCP server in PolicyLayer and add a rule for get_user_info: 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 Hevy. Nothing to install.
get_user_info 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_info 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_info. 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_info is provided by the Hevy MCP server (srdjancodes/hevy-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 →