Get information about the logged-in user.
AI agents call get_user_profile to retrieve information from Perkakasku 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 without modifying, deleting, or executing any operations. It is purely informational (Read category). Severity is low because user profile information, while potentially sensitive, is limited to the authenticated user's own data and does not expose system-wide data or enable further attacks. The tool has minimal blast radius if misused by an AI agent.
From the tool's definition Tool name is 'get_user_profile' and description states it 'Get information about the logged-in user.' This is a retrieval operation with no side effects.
Attacks that exploit this kind of access
Get information about the logged-in user. It is categorised as a Read tool in the Perkakasku MCP Server, which means it retrieves data without modifying state.
Register the Perkakasku 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 Perkakasku. 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 Perkakasku MCP server (perkakasku-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 →