Update a Role
update_roleChange a Role. Omitted fields keep their values. Built-in Roles keep their names and descriptions. Administrator always reaches every approved Request; Member and End users may select Requests. End users has no members. The Administrator Role's toggles are the Project's grants, and changing one is recorded.
Tool call template
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"role_id": "<role_id>"
},
"name": "update_role"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| name | No | A new name | |
| role_id | Yes | UUID of the Role | |
| mcp_level | No | The Role's MCP level: "none", "minimal" or "rich"; omitted preserves the current value. "full" must be confirmed by a person in the member-access pane | |
| description | No | A new description | |
| tool_groups | No | The Role's tool toggles, as an object of toggle names to booleans (addQueryManagement, addDataChangingRequests, addSchemaGovernance, addDatasourceManagement, addOntologyMaintenanceTools, addOntologySuggestions, addWorkflowTools, addWorkflowParticipation). The Administrator Role's toggles are the Project's grants; any other Role uses only the member-facing one (addWorkflowParticipation). Pass the complete set: omitted toggles are turned off. | |
| request_mode | No | "all" or "selected" | |
| datasource_ids | No | UUIDs of the datasources this Role's Rich or Full level applies to. Omitted leaves the list unchanged. Rich and Full need at least one. Adding a datasource to Full must be confirmed by a person; removing one does not. |