Get the logged-in user
AI agents call GET_USER_PROFILE to retrieve information from Travel Agent MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a read operation that queries and retrieves user profile information. It has no side effects and does not modify data. Severity is medium rather than low because user profile data may contain sensitive personal information (name, email, address, payment methods) that could be misused if exposed to an unauthorized agent, though the tool itself performs no destructive or financial action.
From the tool's definition Tool name is GET_USER_PROFILE and description states 'Get the logged-in user', which retrieves user profile data without modification.
Attacks that exploit this kind of access
Get the logged-in user. It is categorised as a Read tool in the Travel Agent MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Travel Agent 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 Travel Agent 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 Travel Agent MCP Server MCP server (nxgnosis/travelagentmcp). 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 →