action1-mcp-server

Move the endpoint to another organization

action1_move_endpoint

Destructive

Move an endpoint to another organization by providing its endpoint ID and target organization ID, with preview by default and explicit confirmation required to execute.

Instructions

Move the endpoint to another organization. Moves the endpoint to another organization. Perm: manage_endpoints.

Input Schema

Name	Required	Description
`body`	Yes	Request body
`org_id`	No	Org UUID.
`confirm`	No	Required to execute. Exact string "YES".
`dry_run`	No	Default true (preview). Set false to execute.
`endpoint_id`	Yes	Provide an endpoint ID.

Output Schema

Name	Required	Description	Default
`OS`	No
`id`	No
`MAC`	No
`NIC`	No
`RAM`	No
`WiFi`	No
`disk`	No
`name`	No
`self`	No
`tool`	No
`type`	No
`user`	No
`video`	No
`custom`	No
`serial`	No
`status`	No
`address`	No
`comment`	No
`dry_run`	No
`CPU_name`	No
`CPU_size`	No
`platform`	No
`CPU_model`	No
`last_seen`	No
`would_send`	No
`device_name`	No
`architecture`	No
`manufacturer`	No
`agent_version`	No
`online_status`	No
`update_status`	No
`last_boot_time`	No
`missing_updates`	No
`organization_id`	No
`reboot_required`	No
`vulnerabilities`	No
`AD_security_groups`	No
`agent_install_date`	No
`subscription_status`	No
`AD_organization_unit`	No
`vulnerability_status`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed47 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"
```
- changedInput schema / properties / body / description
```
Previous value: -"Request body (schema: object)"New value: +"Request body"
```
- addedInput schema / properties / body / properties
```
Added value: +{
+  "target_organization_id": {
+    "description": "The organization where the endpoint will be moved to.",
+    "type": "string"
+  }
+}
```
- addedInput schema / properties / body / required
```
Added value: +[
+  "target_organization_id"
+]
```
- 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 / AD_organization_unit
```
Added value: +{}
```
- addedOutput schema / properties / AD_security_groups
```
Added value: +{}
```
- addedOutput schema / properties / CPU_model
```
Added value: +{}
```
- addedOutput schema / properties / CPU_name
```
Added value: +{}
```
- addedOutput schema / properties / CPU_size
```
Added value: +{}
```
- addedOutput schema / properties / MAC
```
Added value: +{}
```
- addedOutput schema / properties / NIC
```
Added value: +{}
```
- addedOutput schema / properties / OS
```
Added value: +{}
```
- addedOutput schema / properties / RAM
```
Added value: +{}
```
- addedOutput schema / properties / WiFi
```
Added value: +{}
```
- addedOutput schema / properties / address
```
Added value: +{}
```
- addedOutput schema / properties / agent_install_date
```
Added value: +{}
```
- addedOutput schema / properties / agent_version
```
Added value: +{}
```
- addedOutput schema / properties / architecture
```
Added value: +{}
```
- addedOutput schema / properties / comment
```
Added value: +{}
```
- addedOutput schema / properties / custom
```
Added value: +{}
```
- addedOutput schema / properties / device_name
```
Added value: +{}
```
- addedOutput schema / properties / disk
```
Added value: +{}
```
- addedOutput schema / properties / dry_run
```
Added value: +{}
```
- addedOutput schema / properties / id
```
Added value: +{}
```
- addedOutput schema / properties / last_boot_time
```
Added value: +{}
```
- addedOutput schema / properties / last_seen
```
Added value: +{}
```
- addedOutput schema / properties / manufacturer
```
Added value: +{}
```
- addedOutput schema / properties / missing_updates
```
Added value: +{}
```
- addedOutput schema / properties / name
```
Added value: +{}
```
- addedOutput schema / properties / online_status
```
Added value: +{}
```
- addedOutput schema / properties / organization_id
```
Added value: +{}
```
- addedOutput schema / properties / platform
```
Added value: +{}
```
- addedOutput schema / properties / reboot_required
```
Added value: +{}
```
- addedOutput schema / properties / self
```
Added value: +{}
```
- addedOutput schema / properties / serial
```
Added value: +{}
```
- addedOutput schema / properties / status
```
Added value: +{}
```
- addedOutput schema / properties / subscription_status
```
Added value: +{}
```
- addedOutput schema / properties / tool
```
Added value: +{}
```
- addedOutput schema / properties / type
```
Added value: +{}
```
- addedOutput schema / properties / update_status
```
Added value: +{}
```
- addedOutput schema / properties / user
```
Added value: +{}
```
- addedOutput schema / properties / video
```
Added value: +{}
```
- addedOutput schema / properties / vulnerabilities
```
Added value: +{}
```
- addedOutput schema / properties / vulnerability_status
```
Added value: +{}
```
- addedOutput schema / properties / would_send
```
Added value: +{}
```
First observedv0.5.0Jun 27, 2026

TDQS

B3.1/5.0

Behavior3/5

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

Annotations already flag destructive=true, idempotent=false and openWorldHint=true, so the safety profile is largely covered. The description adds the permission requirement, which is genuinely beyond the annotations, but says nothing about the confirm="YES" gate or dry-run default that the schema carries, leaving a destructive operation thinly explained.

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

Conciseness3/5

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

It is short and front-loaded, but one of three sentences is a verbatim restatement of the first, which is pure waste. The permission note is well placed at the end.

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?

With a full output schema, 100% parameter coverage and complete annotations, the description need not explain return values or field formats. However, for a destructive cross-org move it omits the confirmation/dry-run safety semantics and the consequence of removing the endpoint from its current organization, which an agent would benefit from knowing before calling.

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 endpoint_id, target_organization_id, org_id, confirm and dry_run are already documented at the field level. The description's only semantic contribution is confirming that 'another organization' is the target, which maps to an existing parameter rather than adding new meaning.

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 (move the endpoint to another organization), so the action is unambiguous. It does not differentiate from near-siblings like action1_update_endpoint or action1_delete_endpoint, and the second sentence merely repeats the first.

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?

The only contextual note is the required permission (manage_endpoints), which is useful as a prerequisite. There is no guidance on when to use this rather than action1_update_endpoint, nor any mention of the requirement that the target org be valid or that the endpoint leaves its current org.

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

Deploy Server