action1-mcp-server

Update Agent Deployment settings

action1_update_endpoint_agent_deployment

Destructive

Update an organization's endpoint agent deployment settings to configure AD domains, computer lists, and discovery exclusions, with optional preview before execution.

Instructions

Update Agent Deployment settings. Updates the Agent Deployment configuration for a specific organization. Perm: manage_endpoints.

Input Schema

Name	Required	Description
`body`	No	Request body (schema: AgentDeploymentPayload)
`org_id`	No	Org UUID.
`confirm`	No	Required to execute. Exact string "YES".
`dry_run`	No	Default true (preview). Set false to execute.

Output Schema

Name	Required	Description	Default
`tool`	No
`dry_run`	No
`would_send`	No
`connector_id`	No
`connector_name`	No
`connector_status`	No
`connector_last_seen`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed11 schema fields changedv0.6.0Oct 26, 2026

changedInput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

addedInput schema / properties / body / properties

Added value: +{
+  "ad_domain": {
+    "description": "1 - AD domain, 0 - computer list.",
+    "enum": [
+      "0",
+      "1"
+    ],
+    "type": "string"
+  },
+  "computer_list": {
+    "description": "The list of computers.",
+    "items": {
+      "type": "string"
+    },
+    "type": "array"
+  },
+  "domain_name": {
+    "description": "A comma-separated list of AD domains.\"",
+    "type": "string"
+  },
+  "exclude_DCs": {
+    "description": "A setting to exclude domain controllers from discovery by Action1 Deployment.",
+    "enum": [
+      "yes",
+      "no"
+    ],
+    "type": "string"
+  },
+  "exclude_computer_list": {
+    "description": "Excluded machines.",
+    "items": {
+      "type": "string"
+    },
+    "type": "array"
+  },
+  "exclude_computer_list_enabled": {
+    "description": "A setting to exclude certain machines from discovery by Action1 Deployment.",
+    "enum": [
+      "yes",
+      "no"
+    ],
+    "type": "string"
+  },
+  "exclude_servers": {
+    "description": "A setting to exclude servers from discovery by Action1 Deployment.",
+    "enum": [
+      "yes",
+      "no"
+    ],
+    "type": "string"
+  },
+  "exclude_workstations": {
+    "description": "A setting to exclude workstations from discovery by Action1 Deployment.",
+    "enum": [
+      "yes",
+      "no"
+    ],
+    "type": "string"
+  }
+}

changedOutput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

changedOutput schema / additionalProperties
```
Previous value: -trueNew value: +{}
```
addedOutput schema / properties / connector_id
```
Added value: +{}
```
addedOutput schema / properties / connector_last_seen
```
Added value: +{}
```
addedOutput schema / properties / connector_name
```
Added value: +{}
```
addedOutput schema / properties / connector_status
```
Added value: +{}
```
addedOutput schema / properties / dry_run
```
Added value: +{}
```
addedOutput schema / properties / tool
```
Added value: +{}
```
addedOutput schema / properties / would_send
```
Added value: +{}
```

First observedv0.5.0Jun 27, 2026

TDQS

B3.2/5.0

Behavior3/5

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

Annotations already declare destructiveHint=true, openWorldHint=true, and not idempotent, so the safety profile is largely carried for the agent. The description adds one piece of context not present in the structured fields — the required permission 'manage_endpoints' — but says nothing about what existing configuration is overwritten, whether the update is partial or full, or that a confirmation/dry-run gate exists (which only appears in the schema).

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?

Two short sentences, front-loaded with the action. The second sentence is nearly a restatement of the first ('Update Agent Deployment settings' / 'Updates the Agent Deployment configuration'), which is minor waste but not harmful.

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

Completeness3/5

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

The tool has an output schema and full schema coverage, so return values and parameter shapes are covered elsewhere. However, this is a destructive mutation gated behind confirm="YES" and dry_run-defaulting-to-true, and the description never signals that preview/execute flow — for a destructive write tool that is a meaningful omission even with annotations present.

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 coverage is 100%, so the nested body fields, org_id, confirm, and dry_run are all documented in the schema itself; the description correctly does not need to repeat them. It also adds no syntax or format insight of its own, so the baseline of 3 applies.

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?

The description names a specific verb and resource (update Agent Deployment settings) and adds a scope qualifier the title lacks ('for a specific organization'). The second sentence largely restates the first, and it never distinguishes this from neighboring deployment/discovery tools like get_endpoint_discovery_settings or create_endpoint_group, so it stops short of a 5.

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

Usage Guidelines2/5

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

There is no guidance on when to reach for this tool versus alternatives, nor any stated prerequisites beyond the permission token. The 'Perm: manage_endpoints' line hints at an access requirement but is not framed as a usage condition or exclusion.

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

Deploy Server