dsh-relay

Overview Schema Source Related Servers Discussions Admin

Dispatch a read-only Harness review

start_review

Review specified workspace paths in a read-only Harness session using an approved model, then monitor the run until it completes.

Instructions

Create or reuse a native Harness session with the permission preset fixed to read-only. Exact provider, model, and authorizationBasis are required so the user's existing named-model request is machine-identifiable on the first attempt; do not ask the user to repeat that authorization solely because provider processing is external. Task parameters are path-reference-only: provide the authorized workspace, reviewTargets, contextReadScope, excludedPaths, writeScope, and acceptance criteria. reviewTargets identify what to assess; they are not a read whitelist. contextReadScope declares where Harness may search and read supporting implementation, tests, configuration, and architecture material. Never embed source text, diffs, file dumps, encoded source, or repository archives. Harness reads named files from the authorized workspace itself. These fields are task instructions, not enforced per-path filesystem isolation. The selected Harness model may send content it reads to its configured model provider even though Relay itself uses a loopback address. After start succeeds, share webUrl and keep wait_run until succeeded/failed/cancelled/needs_attention. The calling agent MUST read assistantText before claiming the review is done. If the parent user asked to review then fix, apply accepted findings only after the run is terminal; do not treat a still-running review as finished.

Input Schema

TableJSON Schema

Name	Required	Description
`task`	No	Task parameters are path-reference-only: provide the authorized workspace, reviewTargets, contextReadScope, excludedPaths, writeScope, and acceptance criteria. reviewTargets identify what to assess; they are not a read whitelist. contextReadScope declares where Harness may search and read supporting implementation, tests, configuration, and architecture material. Never embed source text, diffs, file dumps, encoded source, or repository archives. Harness reads named files from the authorized workspace itself. These fields are task instructions, not enforced per-path filesystem isolation. The selected Harness model may send content it reads to its configured model provider even though Relay itself uses a loopback address.
`model`	Yes	Exact model returned by list_capabilities. Required so approval can identify the content-processing destination.
`content`	No	Task parameters are path-reference-only: provide the authorized workspace, reviewTargets, contextReadScope, excludedPaths, writeScope, and acceptance criteria. reviewTargets identify what to assess; they are not a read whitelist. contextReadScope declares where Harness may search and read supporting implementation, tests, configuration, and architecture material. Never embed source text, diffs, file dumps, encoded source, or repository archives. Harness reads named files from the authorized workspace itself. These fields are task instructions, not enforced per-path filesystem isolation. The selected Harness model may send content it reads to its configured model provider even though Relay itself uses a loopback address.
`provider`	Yes	Exact provider returned by list_capabilities. Required so approval can identify the content-processing destination.
`sessionId`	No
`workspace`	Yes	Authorized absolute Harness workspace root; Harness reads named in-scope files from here.
`writeScope`	No	Paths Harness may modify. Must be empty for read-only runs; this is an instruction declaration in addition to native permissions.
`agentPreset`	No
`openBrowser`	No	Keep false unless the user explicitly asks to open the Harness page in the OS browser.
`sessionMode`	No
`excludedPaths`	No	Paths excluded from contextual reading. This is an instruction declaration, not filesystem enforcement.
`reviewTargets`	No	Subjects to assess. This is not a read whitelist; supply together with contextReadScope.
`idempotencyKey`	No
`reasoningEffort`	No
`contextReadScope`	No	Workspace paths Harness may search and read for evidence. Use only the targets when the user explicitly requests a target-only review.
`authorizationBasis`	Yes	Truthful evidence that the user explicitly selected Harness or this named Harness model to inspect the stated workspace scope. The current explicit request is sufficient authorization for that selected provider to process in-scope reads; do not ask the user to repeat authorization solely because provider processing is external. This field does not broaden the workspace, scope, permissions, destination, or allowed external actions.

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedv0.2.17Sep 16, 2026

changedInput schema / properties / authorizationBasis / description

Previous value: -"Truthful evidence that the user explicitly selected Harness to inspect this workspace. Set only when the current conversation contains that instruction. This records evidence and does not expand permissions or guarantee approval."New value: +"Truthful evidence that the user explicitly selected Harness or this named Harness model to inspect the stated workspace scope. The current explicit request is sufficient authorization for that selected provider to process in-scope reads; do not ask the user to repeat authorization solely because provider processing is external. This field does not broaden the workspace, scope, permissions, destination, or allowed external actions."

addedInput schema / properties / model / description

Added value: +"Exact model returned by list_capabilities. Required so approval can identify the content-processing destination."

addedInput schema / properties / provider / description

Added value: +"Exact provider returned by list_capabilities. Required so approval can identify the content-processing destination."

changedInput schema / required

Previous value: -[
-  "workspace"
-]New value: +[
+  "workspace",
+  "provider",
+  "model",
+  "authorizationBasis"
+]

Changed9 schema fields changedv0.2.13Sep 10, 2026

addedInput schema / properties / authorizationBasis

Added value: +{
+  "const": "explicit-user-request",
+  "description": "Truthful evidence that the user explicitly selected Harness to inspect this workspace. Set only when the current conversation contains that instruction. This records evidence and does not expand permissions or guarantee approval.",
+  "type": "string"
+}

changedInput schema / properties / content / description

Previous value: -"Task parameters are path-reference-only: provide the authorized workspace, file or directory locations, scope, and acceptance criteria. Never embed source text, diffs, file dumps, encoded source, or repository archives. Harness reads named files from the authorized workspace itself. This rule is identical for read-only and write-capable permissions."New value: +"Task parameters are path-reference-only: provide the authorized workspace, reviewTargets, contextReadScope, excludedPaths, writeScope, and acceptance criteria. reviewTargets identify what to assess; they are not a read whitelist. contextReadScope declares where Harness may search and read supporting implementation, tests, configuration, and architecture material. Never embed source text, diffs, file dumps, encoded source, or repository archives. Harness reads named files from the authorized workspace itself. These fields are task instructions, not enforced per-path filesystem isolation. The selected Harness model may send content it reads to its configured model provider even though Relay itself uses a loopback address."

changedInput schema / properties / content / items / oneOf

Previous value: -[
-  {
-    "properties": {
-      "text": {
-        "description": "Task parameters are path-reference-only: provide the authorized workspace, file or directory locations, scope, and acceptance criteria. Never embed source text, diffs, file dumps, encoded source, or repository archives. Harness reads named files from the authorized workspace itself. This rule is identical for read-only and write-capable permissions.",
-        "maxLength": 100000,
-        "type": "string"
-      },
-      "type": {
-        "const": "text",
-        "type": "string"
-      }
-    },
-    "required": [
-      "type",
-      "text"
-    ],
-    "type": "object"
-  },
-  {
-    "properties": {
-      "data": {
-        "minLength": 1,
-        "type": "string"
-      },
-      "mediaType": {
-        "enum": [
-          "image/png",
-          "image/jpeg",
-          "image/webp",
-          "image/gif"
-        ],
-        "type": "string"
-      },
-      "name": {
-        "type": "string"
-      },
-      "type": {
-        "const": "image",
-        "type": "string"
-      }
-    },
-    "required": [
-      "type",
-      "mediaType",
-      "data"
-    ],
-    "type": "object"
-  }
-]New value: +[
+  {
+    "properties": {
+      "text": {
+        "description": "Task parameters are path-reference-only: provide the authorized workspace, reviewTargets, contextReadScope, excludedPaths, writeScope, and acceptance criteria. reviewTargets identify what to assess; they are not a read whitelist. contextReadScope declares where Harness may search and read supporting implementation, tests, configuration, and architecture material. Never embed source text, diffs, file dumps, encoded source, or repository archives. Harness reads named files from the authorized workspace itself. These fields are task instructions, not enforced per-path filesystem isolation. The selected Harness model may send content it reads to its configured model provider even though Relay itself uses a loopback address.",
+        "maxLength": 100000,
+        "type": "string"
+      },
+      "type": {
+        "const": "text",
+        "type": "string"
+      }
+    },
+    "required": [
+      "type",
+      "text"
+    ],
+    "type": "object"
+  },
+  {
+    "properties": {
+      "data": {
+        "minLength": 1,
+        "type": "string"
+      },
+      "mediaType": {
+        "enum": [
+          "image/png",
+          "image/jpeg",
+          "image/webp",
+          "image/gif"
+        ],
+        "type": "string"
+      },
+      "name": {
+        "type": "string"
+      },
+      "type": {
+        "const": "image",
+        "type": "string"
+      }
+    },
+    "required": [
+      "type",
+      "mediaType",
+      "data"
+    ],
+    "type": "object"
+  }
+]

addedInput schema / properties / contextReadScope

Added value: +{
+  "description": "Workspace paths Harness may search and read for evidence. Use only the targets when the user explicitly requests a target-only review.",
+  "items": {
+    "description": "Workspace-relative path, or an absolute path contained by the authorized workspace.",
+    "minLength": 1,
+    "type": "string"
+  },
+  "minItems": 1,
+  "type": "array"
+}

addedInput schema / properties / excludedPaths

Added value: +{
+  "description": "Paths excluded from contextual reading. This is an instruction declaration, not filesystem enforcement.",
+  "items": {
+    "description": "Workspace-relative path, or an absolute path contained by the authorized workspace.",
+    "minLength": 1,
+    "type": "string"
+  },
+  "type": "array"
+}

addedInput schema / properties / openBrowser / description

Added value: +"Keep false unless the user explicitly asks to open the Harness page in the OS browser."

addedInput schema / properties / reviewTargets

Added value: +{
+  "description": "Subjects to assess. This is not a read whitelist; supply together with contextReadScope.",
+  "items": {
+    "description": "Workspace-relative path, or an absolute path contained by the authorized workspace.",
+    "minLength": 1,
+    "type": "string"
+  },
+  "minItems": 1,
+  "type": "array"
+}

changedInput schema / properties / task / description

Previous value: -"Task parameters are path-reference-only: provide the authorized workspace, file or directory locations, scope, and acceptance criteria. Never embed source text, diffs, file dumps, encoded source, or repository archives. Harness reads named files from the authorized workspace itself. This rule is identical for read-only and write-capable permissions."New value: +"Task parameters are path-reference-only: provide the authorized workspace, reviewTargets, contextReadScope, excludedPaths, writeScope, and acceptance criteria. reviewTargets identify what to assess; they are not a read whitelist. contextReadScope declares where Harness may search and read supporting implementation, tests, configuration, and architecture material. Never embed source text, diffs, file dumps, encoded source, or repository archives. Harness reads named files from the authorized workspace itself. These fields are task instructions, not enforced per-path filesystem isolation. The selected Harness model may send content it reads to its configured model provider even though Relay itself uses a loopback address."

addedInput schema / properties / writeScope

Added value: +{
+  "description": "Paths Harness may modify. Must be empty for read-only runs; this is an instruction declaration in addition to native permissions.",
+  "items": {
+    "description": "Workspace-relative path, or an absolute path contained by the authorized workspace.",
+    "minLength": 1,
+    "type": "string"
+  },
+  "type": "array"
+}

Changed4 schema fields changedv0.2.9Sep 1, 2026

addedInput schema / properties / content / description

Added value: +"Task parameters are path-reference-only: provide the authorized workspace, file or directory locations, scope, and acceptance criteria. Never embed source text, diffs, file dumps, encoded source, or repository archives. Harness reads named files from the authorized workspace itself. This rule is identical for read-only and write-capable permissions."

changedInput schema / properties / content / items / oneOf

Previous value: -[
-  {
-    "properties": {
-      "text": {
-        "maxLength": 100000,
-        "type": "string"
-      },
-      "type": {
-        "const": "text",
-        "type": "string"
-      }
-    },
-    "required": [
-      "type",
-      "text"
-    ],
-    "type": "object"
-  },
-  {
-    "properties": {
-      "data": {
-        "minLength": 1,
-        "type": "string"
-      },
-      "mediaType": {
-        "enum": [
-          "image/png",
-          "image/jpeg",
-          "image/webp",
-          "image/gif"
-        ],
-        "type": "string"
-      },
-      "name": {
-        "type": "string"
-      },
-      "type": {
-        "const": "image",
-        "type": "string"
-      }
-    },
-    "required": [
-      "type",
-      "mediaType",
-      "data"
-    ],
-    "type": "object"
-  }
-]New value: +[
+  {
+    "properties": {
+      "text": {
+        "description": "Task parameters are path-reference-only: provide the authorized workspace, file or directory locations, scope, and acceptance criteria. Never embed source text, diffs, file dumps, encoded source, or repository archives. Harness reads named files from the authorized workspace itself. This rule is identical for read-only and write-capable permissions.",
+        "maxLength": 100000,
+        "type": "string"
+      },
+      "type": {
+        "const": "text",
+        "type": "string"
+      }
+    },
+    "required": [
+      "type",
+      "text"
+    ],
+    "type": "object"
+  },
+  {
+    "properties": {
+      "data": {
+        "minLength": 1,
+        "type": "string"
+      },
+      "mediaType": {
+        "enum": [
+          "image/png",
+          "image/jpeg",
+          "image/webp",
+          "image/gif"
+        ],
+        "type": "string"
+      },
+      "name": {
+        "type": "string"
+      },
+      "type": {
+        "const": "image",
+        "type": "string"
+      }
+    },
+    "required": [
+      "type",
+      "mediaType",
+      "data"
+    ],
+    "type": "object"
+  }
+]

addedInput schema / properties / task / description

Added value: +"Task parameters are path-reference-only: provide the authorized workspace, file or directory locations, scope, and acceptance criteria. Never embed source text, diffs, file dumps, encoded source, or repository archives. Harness reads named files from the authorized workspace itself. This rule is identical for read-only and write-capable permissions."

addedInput schema / properties / workspace / description

Added value: +"Authorized absolute Harness workspace root; Harness reads named in-scope files from here."

First observedv0.2.6Aug 30, 2026

TDQS

A4.6/5.0

Behavior5/5

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

The description goes well beyond the sparse annotations by disclosing that the Harness model may send read content to an external provider, that fields are instructions rather than enforced filesystem isolation, and that source text must never be embedded. It also clarifies the post-run lifecycle and the requirement to read assistantText.

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?

The description is dense but purposeful, with important caveats about path-reference-only usage, external processing, and terminal-state handling. It is one long paragraph rather than structured bullets, but each sentence earns its place for a tool with this complexity.

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?

For a 16-parameter tool with no output schema and minimal annotations, the description is remarkably complete: it explains required fields, parameter semantics, data-flow caveats, success behavior, and post-run obligations. The caller knows what to provide, what will happen, and how to avoid prematurely reporting completion.

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

Parameters4/5

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

The description adds real meaning to key parameters: reviewTargets are not a read whitelist, contextReadScope defines where Harness may search, writeScope must be empty for read-only runs, and authorizationBasis should not require repeated user confirmation. However, optional parameters like sessionId, agentPreset, reasoningEffort, and sessionMode remain unexplained despite moderate schema coverage.

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 title and first sentence clearly state a specific action: create or reuse a Harness session with a read-only permission preset to dispatch a review. This distinguishes it from sibling tools like start_run or steer_run because it names the review workflow and the read-only constraint.

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

Usage Guidelines4/5

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

The description gives clear operating context: exact provider/model/authorizationBasis are required, task parameters are path-reference-only, and the caller must wait for terminal status and read assistantText before claiming completion. It does not explicitly name alternatives or say 'use this instead of X,' but the context is strong enough to guide selection.

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

Dispatch a read-only Harness review

Instructions

Input Schema

Schema Changelog

TDQS

Other Tools