Update the logged-in user
AI agents use EDIT_USER_PROFILE to create or update resources in Travel Agent MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Travel Agent MCP Server environment.
The tool updates user profile information, which is a reversible modification (Write category). Severity is medium because unauthorized profile edits could expose or alter personal information, but the blast radius is limited to the authenticated user's account data, not system-wide or financial assets.
From the tool's definition Tool name 'EDIT_USER_PROFILE' and description 'Update the logged-in user' indicate modification of user data. This is a write operation that creates or modifies data reversibly.
Attacks that exploit this kind of access
Update the logged-in user. It is categorised as a Write tool in the Travel Agent MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Travel Agent MCP Server MCP server in PolicyLayer and add a rule for EDIT_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.
EDIT_USER_PROFILE is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the EDIT_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 EDIT_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.
EDIT_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 →