Cancel an active work session without logging changes.
AI agents call cancel_work_session to permanently remove resources in Eureka Labo Task Management MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Cancelling a work session without logging changes is an irreversible action: the session state and any unlogged changes are permanently discarded. This qualifies as Destructive since the session data cannot be recovered after cancellation. Severity is medium because it affects a single work session rather than broader project data.
From the tool's definition 'Cancel an active work session without logging changes' — cancelling without logging means any work-in-progress session data is irreversibly discarded/lost
Attacks that exploit this kind of access
Cancel an active work session without logging changes. It is categorised as a Destructive tool in the Eureka Labo Task Management MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Eureka Labo Task Management MCP Server MCP server in PolicyLayer and add a rule for cancel_work_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 Eureka Labo Task Management MCP Server. Nothing to install.
cancel_work_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_work_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_work_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_work_session is provided by the Eureka Labo Task Management MCP Server MCP server (mazemaze/mcp-server). 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 →