Permanently close the logged-in user
AI agents call CLOSE_ACCOUNT to permanently remove resources in Travel Agent MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Account closure is an irreversible destructive action that cannot be undone without administrative intervention. This represents maximum severity because it destroys user access, associated data, and potentially financial/booking records. The word 'Permanently' explicitly signals non-reversibility.
From the tool's definition Tool name 'CLOSE_ACCOUNT' combined with description 'Permanently close the logged-in user' indicates irreversible deletion or deactivation of user account data and access.
Attacks that exploit this kind of access
Permanently close the logged-in user. It is categorised as a Destructive tool in the Travel Agent MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Travel Agent MCP Server MCP server in PolicyLayer and add a rule for CLOSE_ACCOUNT: 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.
CLOSE_ACCOUNT is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the CLOSE_ACCOUNT 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 CLOSE_ACCOUNT. 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.
CLOSE_ACCOUNT 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 →