droost_entity_update

Droost: Entity Update

droost_entity_update Write (gated)

Module: Droost core

Updates fields on an existing content entity through the entity API. Refuses config entities with a pointer to droost_config_set — that split keeps validation honest. Gated.

Example call

{
    "tool": "droost_entity_update",
    "arguments": {
        "entity_type": "node",
        "id": "1",
        "values": {
            "sticky": 0
        }
    }
}

Example response — captured live on this site

{
    "success": false,
    "message": "This tool is disabled. Enable it with: drush config:set droost.settings allow_destructive true (or via Admin → Configuration → Development → Droost), then reload the MCP server in your editor — the running server caches this flag at startup and will keep refusing until it is restarted. (To disable later, use --input-format=yaml false so the value is stored as a real boolean.)",
    "data": null
}

Updates fields on an existing entity. Provide "entity_type", "id", and "values" (a field => value map of changes). Disabled unless droost.settings.allow_destructive is on, and only over the CLI/STDIO transport.

Input schema (JSON Schema)

{
    "type": "object",
    "properties": {
        "entity_type": {
            "type": "string",
            "description": "Entity type machine name, e.g. \"node\", \"user\"."
        },
        "id": {
            "type": "string",
            "description": "The ID of the entity to update."
        },
        "values": {
            "type": "object",
            "description": "Field => value map of changes to apply, e.g. {\"status\":1}."
        }
    },
    "required": [
        "entity_type",
        "id",
        "values"
    ]
}