List the logged-in user
AI agents call GET_IMMIGRATION_TRANSACTIONS 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 tool retrieves information about the logged-in user without any side effects. It performs a simple query operation that does not create, modify, delete, or execute any actions. The scope is limited to querying user information.
From the tool's definition Tool name 'GET_IMMIGRATION_TRANSACTIONS' and description 'List the logged-in user' indicate data retrieval with no modification. The verb 'List' and lack of any modification language (create, delete, update, execute) confirm this is a read-only operation.
Attacks that exploit this kind of access
List 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_IMMIGRATION_TRANSACTIONS: 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_IMMIGRATION_TRANSACTIONS 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_IMMIGRATION_TRANSACTIONS 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_IMMIGRATION_TRANSACTIONS. 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_IMMIGRATION_TRANSACTIONS 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 →