Get current user details from XAPIHub API
AI agents call get_current_user to retrieve information from XAPIHub MCP Extension 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 an API. It performs a read-only operation that queries data without creating, modifying, deleting, or executing code. The severity is low because the blast radius of misuse is limited to exposure of the current user's own details, which is typically already accessible to an authenticated user. No destructive, financial, or external execution capabilities are present.
From the tool's definition Tool name 'get_current_user' and description 'Get current user details from XAPIHub API' indicate a retrieval operation that queries user information without modification or side effects.
Attacks that exploit this kind of access
Get current user details from XAPIHub API. It is categorised as a Read tool in the XAPIHub MCP Extension MCP Server, which means it retrieves data without modifying state.
Register the XAPIHub MCP Extension MCP server in PolicyLayer and add a rule for get_current_user: 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 XAPIHub MCP Extension. Nothing to install.
get_current_user 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_current_user 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_current_user. 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_current_user is provided by the XAPIHub MCP Extension MCP server (pamithwelikala123/mcp-cursor). 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 →