Horizon MCP Server

update_global_policies

DestructiveIdempotent

Modify global VDI policies for USB, clipboard, and multimedia redirection. Read current settings first, change only intended fields, and pass the full updated object.

Instructions

Update global VDI policies (USB redirection, clipboard, multimedia redirection).

Always call get_global_policies first to read current values. Only modify the specific fields you intend to change — pass the full object back.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`spec`	Yes	Updated global policies object. Call get_global_policies first, modify only the fields you intend to change, then pass the full object here.
`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.

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

A4.5/5.0

Behavior4/5

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

The annotations already declare destructiveHint=true and idempotentHint=true, so the safety profile is covered. The description adds meaningful procedural context: read current values first and preserve unmodified fields, which helps avoid accidental destructive changes. It does not further explain the destructive implications or confirmation behavior, but that is largely covered by annotations and schema.

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

Conciseness5/5

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

Three short sentences, front-loaded with the action and scope, followed by the critical usage constraint. Every sentence earns its place with no repetition or filler.

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

Completeness5/5

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

The tool is a mutation with nested object input, but the description covers the key behavioral requirement: read first and preserve unmodified fields. Annotations cover safety, the output schema covers return values, and the input schema documents both parameters in full. Nothing essential for correct invocation is missing.

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 the parameters are already documented. The description's guidance about passing the full object and modifying only specific fields largely repeats the spec parameter's schema description rather than adding new semantic detail. Baseline 3 is appropriate when schema coverage does the heavy lifting.

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

Purpose5/5

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

The description states a specific verb and resource: 'Update global VDI policies', and it narrows the scope with concrete examples (USB redirection, clipboard, multimedia redirection). This distinguishes it from the sibling get_global_policies and from broader update_settings.

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

Usage Guidelines5/5

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

It gives explicit sequencing: always call get_global_policies first, then modify only intended fields, then pass the full object back. That is a clear when/how-to-use instruction rather than vague context.

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

Deploy Server