Cancel a pre-LIVE Luxxon session (REQUESTED or ASSIGNED). For LIVE sessions use end_session — this one will error with INVALID_STATE.
AI agents call cancel_session to permanently remove resources in Luxxon — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Canceling a session is an irreversible action that terminates an active or pending resource allocation. While not a permanent data deletion, it represents destruction of an active contractual/operational state and may result in loss of access, credits, or ability to recover the session.
From the tool's definition Cancel a pre-LIVE Luxxon session (REQUESTED or ASSIGNED)" — cancels and terminates a session, an action that cannot be undone and may forfeit associated resources or financial position (given the server settles payments in USDC per-second).
Attacks that exploit this kind of access
Cancel a pre-LIVE Luxxon session (REQUESTED or ASSIGNED). For LIVE sessions use end_session — this one will error with INVALID_STATE. It is categorised as a Destructive tool in the Luxxon MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Luxxon MCP server in PolicyLayer and add a rule for cancel_session: 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 Luxxon. Nothing to install.
cancel_session 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 cancel_session 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 cancel_session. 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.
cancel_session is provided by the Luxxon MCP server (luxxon-dev/luxxon-sdk). 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 →