Horizon MCP Server

logoff_sessions

Destructive

Terminate user sessions and close running applications to free up VDI resources. Use with caution as unsaved data will be lost.

Instructions

Log off one or more user sessions, terminating their running applications.

CAUTION: This will close all running applications in the session. Unsaved data will be lost. Always confirm with the user before calling this.

Input Schema

TableJSON Schema

Name	Required	Description
`forced`	No	If true, log off locked sessions. If false, locked sessions are skipped.
`confirm`	No	Only used when the server runs with HORIZON_CONFIRMATION=flag (clients without elicitation). Otherwise the user is asked to confirm directly in the client.
`session_ids`	Yes	List of session IDs to log off

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv0.2.0Sep 30, 2026

addedInput schema / properties / confirm

Added value: +{
+  "default": false,
+  "description": "Only used when the server runs with HORIZON_CONFIRMATION=flag (clients without elicitation). Otherwise the user is asked to confirm directly in the client.",
+  "type": "boolean"
+}

First observedv0.1.0Sep 10, 2026

TDQS

A3.7/5.0

Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare destructiveHint=true and readOnlyHint=false, but the description adds concrete impact detail beyond them: running applications are closed and unsaved data is lost. The explicit user-confirmation requirement is useful behavioral context. It stops short of explaining interaction with the forced/confirm parameters, which the schema covers.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three short sentences with the action front-loaded and the caution clearly delineated. Efficient, though the warning repeats the destructive implication already carried by the annotations, adding slight redundancy.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With an output schema present and rich annotations, the description only needs to supply safety and confirmation context, which it does. The missing piece is routing among sibling session-termination tools, a minor gap for this otherwise complete definition.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so all three parameters including forced and confirm are already documented in the schema. The description adds only that multiple sessions can be targeted via 'one or more', which is marginal value beyond the schema baseline.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb (log off) plus resource (user sessions) and clarifies the effect (terminating running applications). It does not explicitly differentiate itself from close siblings like disconnect_sessions or reset_or_restart_sessions, leaving the agent to infer the distinction.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Provides a clear precondition (always confirm with the user) but gives no guidance on when to choose this over disconnect_sessions or other session-terminating siblings. Usage is implied rather than stated.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server