Skip to main content
Glama
harness

Harness MCP Server

Official
by harness

harness_execute

Destructive

Execute Harness resource actions—run/retry pipelines, toggle feature flags, test connectors, sync GitOps apps, run chaos experiments—using URLs or identifiers, with optional wait for terminal status.

Instructions

Execute an action on a Harness resource: run/retry/interrupt pipelines, kill/restore FME feature flags, test connectors, sync GitOps apps, run chaos experiments. You can pass a Harness URL to auto-extract identifiers. Pass wait: true for pipeline run/retry to block until the execution reaches a terminal status — single tool call instead of an LLM polling loop. For HQL batch operations pass queries with resource_type='hql_query' and action='validate' or 'run'.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlNoHarness UI URL — auto-extracts org, project, type, and ID
bodyNoAdditional body payload for the action
waitNoFor pipeline run/retry actions: block until the execution reaches a terminal status (Success/Failed/Aborted/Errored/Expired). Server-side polling — a single tool call gives the agent the final outcome instead of an LLM polling loop. Ignored for other actions.
actionYesAction to execute (e.g. run, retry, interrupt, toggle, test_connection, sync)
inputsNoPipeline runtime inputs: key-value pairs like {branch: 'main'} (auto-resolved), or full YAML string. Check runtime_input_template first via harness_get.
org_idNoOrganization identifier. Required for org- and project-scoped resources unless a Harness URL is passed. This session has no configured default (common in hosted/multi-user HTTP) — pass the current org_id on the first call. Do not omit it.
paramsNoAction-specific parameters. Call harness_describe for available fields per resource_type.
confirmNoSet to true to confirm the operation. Only required when the action's risk is medium_write or above (e.g. pipeline.run is high_write; hql_query.run/validate are read and need no confirmation) AND the client cannot surface a confirmation prompt — e.g. managed MCP that does not advertise elicitation, or an elicitation that fails at runtime. Has no effect for low-risk actions. Does NOT override an explicit decline from a client that completed an elicitation prompt — a user's decline is authoritative.
queriesNoBatch HQL queries — use with resource_type='hql_query' and action='validate' or 'run'. Fans out in parallel, returns per-query results.
project_idNoProject identifier. Required for project-scoped resources unless a Harness URL is passed. This session has no configured default (common in hosted/multi-user HTTP) — pass the current project_id on the first call. Do not omit it.
resource_idNoPrimary resource identifier
input_set_idsNoInput set IDs for complex pipelines. List available: harness_list(resource_type='input_set', filters={pipeline_id: '...'}).
resource_typeNoResource type with executable actions. Auto-detected from url.
resource_scopeNoScope for the operation. account: account-level resources only — do not use account to skip a known org/project. org: org-level (org_id). project: org+project. Omit to use the resource's default scope. Auto-detected from url when present.
wait_timeout_secondsNoMax seconds to wait when wait=true. Default 600 (10 min). Max 7200 (2 h). When the timeout fires, returns execution_timed_out=true with the last observed status.
wait_poll_interval_secondsNoInitial poll interval when wait=true (seconds). Default 3. Backoff multiplier 1.5x, capped at 30s.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed4 schema fields changedv3.2.22
    • changedInput schema / properties / org_id / description
      Previous value: -"Organization identifier (overrides default)"New value: +"Organization identifier. Required for org- and project-scoped resources unless a Harness URL is passed. This session has no configured default (common in hosted/multi-user HTTP) — pass the current org_id on the first call. Do not omit it."
    • changedInput schema / properties / project_id / description
      Previous value: -"Project identifier (overrides default)"New value: +"Project identifier. Required for project-scoped resources unless a Harness URL is passed. This session has no configured default (common in hosted/multi-user HTTP) — pass the current project_id on the first call. Do not omit it."
    • changedInput schema / properties / resource_scope / description
      Previous value: -"Scope for the operation. account: omit org/project (e.g. /v1/templates). org: org only. project: org+project. Auto-detected from url when present."New value: +"Scope for the operation. account: account-level resources only — do not use account to skip a known org/project. org: org-level (org_id). project: org+project. Omit to use the resource's default scope. Auto-detected from url when present."
    • changedInput schema / properties / resource_type / enum
      Previous value: -[
      -  "approval_instance",
      -  "attestation",
      -  "chaos_action",
      -  "chaos_action_template",
      -  "chaos_experiment",
      -  "chaos_experiment_template",
      -  "chaos_fault",
      -  "chaos_fault_template",
      -  "chaos_guard_rule",
      -  "chaos_k8s_infrastructure",
      -  "chaos_loadtest",
      -  "chaos_probe",
      -  "chaos_probe_template",
      -  "chaos_risk_scan",
      -  "chaos_service",
      -  "commit",
      -  "connector",
      -  "cost_anomaly",
      -  "cost_budget",
      -  "cost_perspective",
      -  "cost_perspective_folder",
      -  "cost_recommendation",
      -  "database_execute_llm_authoring_pipeline",
      -  "delegate_token",
      -  "environment",
      -  "eval_annotation",
      -  "eval_dataset",
      -  "eval_dataset_item",
      -  "eval_git_registration",
      -  "eval_metric",
      -  "eval_metric_set",
      -  "eval_run",
      -  "eval_suite",
      -  "eval_target",
      -  "evaluation",
      -  "execution",
      -  "file_content",
      -  "file_store",
      -  "fme_feature_flag",
      -  "fme_feature_flag_definition",
      -  "fme_rule_based_segment_definition",
      -  "freeze_window",
      -  "gitops_application",
      -  "global_freeze",
      -  "hql_query",
      -  "idp_workflow",
      -  "incident",
      -  "infrastructure",
      -  "online_eval",
      -  "pipeline",
      -  "pipeline_dynamic_execution",
      -  "pipeline_v1",
      -  "pr_reviewer",
      -  "pull_request",
      -  "scanned_risk",
      -  "scs_sbom_drift",
      -  "security_exemption",
      -  "user"
      -]New value: +[
      +  "alert",
      +  "approval_instance",
      +  "attestation",
      +  "chaos_action",
      +  "chaos_action_template",
      +  "chaos_experiment",
      +  "chaos_experiment_template",
      +  "chaos_fault",
      +  "chaos_fault_template",
      +  "chaos_guard_rule",
      +  "chaos_k8s_infrastructure",
      +  "chaos_loadtest",
      +  "chaos_probe",
      +  "chaos_probe_template",
      +  "chaos_risk_scan",
      +  "chaos_service",
      +  "commit",
      +  "connector",
      +  "cost_anomaly",
      +  "cost_budget",
      +  "cost_perspective",
      +  "cost_perspective_folder",
      +  "cost_recommendation",
      +  "database_execute_llm_authoring_pipeline",
      +  "delegate_token",
      +  "environment",
      +  "eval_annotation",
      +  "eval_dataset",
      +  "eval_dataset_item",
      +  "eval_git_registration",
      +  "eval_metric",
      +  "eval_metric_set",
      +  "eval_run",
      +  "eval_suite",
      +  "eval_target",
      +  "evaluation",
      +  "execution",
      +  "file_content",
      +  "file_store",
      +  "fme_feature_flag",
      +  "fme_feature_flag_definition",
      +  "fme_rule_based_segment_definition",
      +  "freeze_window",
      +  "gitops_application",
      +  "global_freeze",
      +  "hql_query",
      +  "idp_workflow",
      +  "incident",
      +  "infrastructure",
      +  "online_eval",
      +  "pipeline",
      +  "pipeline_dynamic_execution",
      +  "pipeline_v1",
      +  "pr_reviewer",
      +  "pull_request",
      +  "scanned_risk",
      +  "scs_sbom_drift",
      +  "security_exemption",
      +  "user"
      +]
  2. Changed1 schema field changedv3.2.21
    • changedInput schema / properties / resource_type / enum
      Previous value: -[
      -  "approval_instance",
      -  "attestation",
      -  "chaos_action",
      -  "chaos_action_template",
      -  "chaos_experiment",
      -  "chaos_experiment_template",
      -  "chaos_fault",
      -  "chaos_fault_template",
      -  "chaos_guard_rule",
      -  "chaos_k8s_infrastructure",
      -  "chaos_loadtest",
      -  "chaos_probe",
      -  "chaos_probe_template",
      -  "chaos_risk_scan",
      -  "chaos_service",
      -  "commit",
      -  "connector",
      -  "cost_anomaly",
      -  "cost_budget",
      -  "cost_perspective",
      -  "cost_perspective_folder",
      -  "cost_recommendation",
      -  "database_execute_llm_authoring_pipeline",
      -  "delegate_token",
      -  "environment",
      -  "eval_annotation",
      -  "eval_dataset",
      -  "eval_dataset_item",
      -  "eval_git_registration",
      -  "eval_metric",
      -  "eval_metric_set",
      -  "eval_run",
      -  "eval_suite",
      -  "eval_target",
      -  "evaluation",
      -  "execution",
      -  "file_content",
      -  "file_store",
      -  "fme_feature_flag",
      -  "fme_rule_based_segment_definition",
      -  "freeze_window",
      -  "gitops_application",
      -  "global_freeze",
      -  "hql_query",
      -  "idp_workflow",
      -  "incident",
      -  "infrastructure",
      -  "online_eval",
      -  "pipeline",
      -  "pipeline_dynamic_execution",
      -  "pipeline_v1",
      -  "pr_reviewer",
      -  "pull_request",
      -  "scanned_risk",
      -  "scs_sbom_drift",
      -  "security_exemption",
      -  "user"
      -]New value: +[
      +  "approval_instance",
      +  "attestation",
      +  "chaos_action",
      +  "chaos_action_template",
      +  "chaos_experiment",
      +  "chaos_experiment_template",
      +  "chaos_fault",
      +  "chaos_fault_template",
      +  "chaos_guard_rule",
      +  "chaos_k8s_infrastructure",
      +  "chaos_loadtest",
      +  "chaos_probe",
      +  "chaos_probe_template",
      +  "chaos_risk_scan",
      +  "chaos_service",
      +  "commit",
      +  "connector",
      +  "cost_anomaly",
      +  "cost_budget",
      +  "cost_perspective",
      +  "cost_perspective_folder",
      +  "cost_recommendation",
      +  "database_execute_llm_authoring_pipeline",
      +  "delegate_token",
      +  "environment",
      +  "eval_annotation",
      +  "eval_dataset",
      +  "eval_dataset_item",
      +  "eval_git_registration",
      +  "eval_metric",
      +  "eval_metric_set",
      +  "eval_run",
      +  "eval_suite",
      +  "eval_target",
      +  "evaluation",
      +  "execution",
      +  "file_content",
      +  "file_store",
      +  "fme_feature_flag",
      +  "fme_feature_flag_definition",
      +  "fme_rule_based_segment_definition",
      +  "freeze_window",
      +  "gitops_application",
      +  "global_freeze",
      +  "hql_query",
      +  "idp_workflow",
      +  "incident",
      +  "infrastructure",
      +  "online_eval",
      +  "pipeline",
      +  "pipeline_dynamic_execution",
      +  "pipeline_v1",
      +  "pr_reviewer",
      +  "pull_request",
      +  "scanned_risk",
      +  "scs_sbom_drift",
      +  "security_exemption",
      +  "user"
      +]
  3. Changed1 schema field changedv3.2.20
    • changedInput schema / properties / resource_type / enum
      Previous value: -[
      -  "approval_instance",
      -  "chaos_action",
      -  "chaos_action_template",
      -  "chaos_experiment",
      -  "chaos_experiment_template",
      -  "chaos_fault",
      -  "chaos_fault_template",
      -  "chaos_guard_rule",
      -  "chaos_k8s_infrastructure",
      -  "chaos_loadtest",
      -  "chaos_probe",
      -  "chaos_probe_template",
      -  "chaos_risk_scan",
      -  "commit",
      -  "connector",
      -  "cost_anomaly",
      -  "cost_perspective",
      -  "cost_perspective_folder",
      -  "cost_recommendation",
      -  "database_execute_llm_authoring_pipeline",
      -  "delegate_token",
      -  "environment",
      -  "eval_annotation",
      -  "eval_dataset",
      -  "eval_dataset_item",
      -  "eval_git_registration",
      -  "eval_metric",
      -  "eval_metric_set",
      -  "eval_run",
      -  "eval_suite",
      -  "eval_target",
      -  "evaluation",
      -  "execution",
      -  "file_content",
      -  "file_store",
      -  "fme_feature_flag",
      -  "fme_rule_based_segment_definition",
      -  "freeze_window",
      -  "gitops_application",
      -  "global_freeze",
      -  "hql_query",
      -  "idp_workflow",
      -  "incident",
      -  "infrastructure",
      -  "online_eval",
      -  "pipeline",
      -  "pipeline_dynamic_execution",
      -  "pipeline_v1",
      -  "pr_reviewer",
      -  "pull_request",
      -  "scanned_risk",
      -  "scs_sbom_drift",
      -  "security_exemption",
      -  "user"
      -]New value: +[
      +  "approval_instance",
      +  "attestation",
      +  "chaos_action",
      +  "chaos_action_template",
      +  "chaos_experiment",
      +  "chaos_experiment_template",
      +  "chaos_fault",
      +  "chaos_fault_template",
      +  "chaos_guard_rule",
      +  "chaos_k8s_infrastructure",
      +  "chaos_loadtest",
      +  "chaos_probe",
      +  "chaos_probe_template",
      +  "chaos_risk_scan",
      +  "chaos_service",
      +  "commit",
      +  "connector",
      +  "cost_anomaly",
      +  "cost_budget",
      +  "cost_perspective",
      +  "cost_perspective_folder",
      +  "cost_recommendation",
      +  "database_execute_llm_authoring_pipeline",
      +  "delegate_token",
      +  "environment",
      +  "eval_annotation",
      +  "eval_dataset",
      +  "eval_dataset_item",
      +  "eval_git_registration",
      +  "eval_metric",
      +  "eval_metric_set",
      +  "eval_run",
      +  "eval_suite",
      +  "eval_target",
      +  "evaluation",
      +  "execution",
      +  "file_content",
      +  "file_store",
      +  "fme_feature_flag",
      +  "fme_rule_based_segment_definition",
      +  "freeze_window",
      +  "gitops_application",
      +  "global_freeze",
      +  "hql_query",
      +  "idp_workflow",
      +  "incident",
      +  "infrastructure",
      +  "online_eval",
      +  "pipeline",
      +  "pipeline_dynamic_execution",
      +  "pipeline_v1",
      +  "pr_reviewer",
      +  "pull_request",
      +  "scanned_risk",
      +  "scs_sbom_drift",
      +  "security_exemption",
      +  "user"
      +]
  4. Changed1 schema field changedv3.2.17
    • changedInput schema / properties / resource_type / enum
      Previous value: -[
      -  "approval_instance",
      -  "chaos_action",
      -  "chaos_action_template",
      -  "chaos_experiment",
      -  "chaos_experiment_template",
      -  "chaos_fault",
      -  "chaos_fault_template",
      -  "chaos_guard_rule",
      -  "chaos_k8s_infrastructure",
      -  "chaos_loadtest",
      -  "chaos_probe",
      -  "chaos_probe_template",
      -  "commit",
      -  "connector",
      -  "cost_anomaly",
      -  "cost_perspective",
      -  "cost_perspective_folder",
      -  "cost_recommendation",
      -  "database_execute_llm_authoring_pipeline",
      -  "delegate_token",
      -  "environment",
      -  "eval_annotation",
      -  "eval_dataset",
      -  "eval_dataset_item",
      -  "eval_git_registration",
      -  "eval_metric",
      -  "eval_metric_set",
      -  "eval_run",
      -  "eval_suite",
      -  "eval_target",
      -  "evaluation",
      -  "execution",
      -  "file_content",
      -  "file_store",
      -  "fme_feature_flag",
      -  "fme_rule_based_segment_definition",
      -  "freeze_window",
      -  "gitops_application",
      -  "global_freeze",
      -  "hql_query",
      -  "idp_workflow",
      -  "incident",
      -  "infrastructure",
      -  "online_eval",
      -  "pipeline",
      -  "pipeline_dynamic_execution",
      -  "pipeline_v1",
      -  "pr_reviewer",
      -  "pull_request",
      -  "scs_sbom_drift",
      -  "security_exemption",
      -  "user"
      -]New value: +[
      +  "approval_instance",
      +  "chaos_action",
      +  "chaos_action_template",
      +  "chaos_experiment",
      +  "chaos_experiment_template",
      +  "chaos_fault",
      +  "chaos_fault_template",
      +  "chaos_guard_rule",
      +  "chaos_k8s_infrastructure",
      +  "chaos_loadtest",
      +  "chaos_probe",
      +  "chaos_probe_template",
      +  "chaos_risk_scan",
      +  "commit",
      +  "connector",
      +  "cost_anomaly",
      +  "cost_perspective",
      +  "cost_perspective_folder",
      +  "cost_recommendation",
      +  "database_execute_llm_authoring_pipeline",
      +  "delegate_token",
      +  "environment",
      +  "eval_annotation",
      +  "eval_dataset",
      +  "eval_dataset_item",
      +  "eval_git_registration",
      +  "eval_metric",
      +  "eval_metric_set",
      +  "eval_run",
      +  "eval_suite",
      +  "eval_target",
      +  "evaluation",
      +  "execution",
      +  "file_content",
      +  "file_store",
      +  "fme_feature_flag",
      +  "fme_rule_based_segment_definition",
      +  "freeze_window",
      +  "gitops_application",
      +  "global_freeze",
      +  "hql_query",
      +  "idp_workflow",
      +  "incident",
      +  "infrastructure",
      +  "online_eval",
      +  "pipeline",
      +  "pipeline_dynamic_execution",
      +  "pipeline_v1",
      +  "pr_reviewer",
      +  "pull_request",
      +  "scanned_risk",
      +  "scs_sbom_drift",
      +  "security_exemption",
      +  "user"
      +]
  5. First observedv3.2.10

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already mark destructive/readOnly/idempotent behavior, and the description adds useful behavioral context beyond them: server-side blocking wait to terminal status, URL auto-extraction of identifiers, and that wait is ignored for non-pipeline actions. It could say more about side effects of disruptive actions like kill or interrupt, but the destructiveHint covers the safety signal.

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 dense sentences front-load the tool's action role, then cover the two most non-obvious usage patterns: URL auto-extraction and blocking wait, plus HQL batch. No filler or repetition of the schema.

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?

For a 16-parameter, open-world action tool, the description plus the highly detailed schema and output schema provide sufficient initial orientation. It does not enumerate every resource_type/action combination, but it points to harness_describe for params and runtime_input_template via harness_get, and uses examples to establish the pattern.

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?

Schema coverage is 100%, so the baseline is 3. The description adds cross-parameter recipes—queries plus resource_type='hql_query' plus action='validate'/'run', and wait plus pipeline run/retry—that are not inferable from individual parameter docs. Since the schema is already very detailed, this is strong but not maximal.

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 uses a specific verb ('Execute an action') and resource ('Harness resource'), then enumerates representative operations that differentiate it from read/list/delete tools: run/retry/interrupt pipelines, kill/restore FME flags, test connectors, sync GitOps, run chaos experiments. This makes its role as the side-effecting action tool unmistakable.

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?

It gives concrete usage recipes: use wait:true for pipeline run/retry to avoid a polling loop, and use queries with resource_type='hql_query' for HQL batch operations. It does not explicitly contrast with sibling tools like harness_update or harness_delete, so it misses the explicit when-not/alternative criterion for a 5.

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

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/harness/mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server