Mark an immigration notification as read.
AI agents use MARK_IMMIGRATION_NOTIFICATION_READ 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.
This tool creates or modifies data in a reversible manner by updating the read/unread status of a notification. It does not delete data, execute arbitrary code, move money, or create irreversible changes. The impact is confined to marking metadata on a single notification, which can be undone by marking it unread again.
From the tool's definition Tool name 'MARK_IMMIGRATION_NOTIFICATION_READ' and description 'Mark an immigration notification as read' indicate modification of a notification state.
Attacks that exploit this kind of access
Mark an immigration notification as read. 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 MARK_IMMIGRATION_NOTIFICATION_READ: 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.
MARK_IMMIGRATION_NOTIFICATION_READ 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 MARK_IMMIGRATION_NOTIFICATION_READ 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 MARK_IMMIGRATION_NOTIFICATION_READ. 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.
MARK_IMMIGRATION_NOTIFICATION_READ 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 →