MCP Tools

Resolve Tool

Tool	Required scope	Purpose
resolve	mcp:resolve	Answer open-ended project routing and responsibility questions.

resolve accepts query, optional project_id, and optional mode (test or live). Use it when the user asks who should handle a task, who to contact, which participant is responsible, or who can act through a delegation.

Status Tools

Tool	Required scope	Purpose
get_status	mcp:status:read	Return sanitized deployment and license status.

get_status returns the active edition, release channel, license state, product limits, feature availability, support tier, term end, and any current license warning. Its retained access compatibility object reports the stable allowed-deployment response used by existing clients.

Example output:

{
  "access": { "allowed": true, "code": "ok", "reason": null },
  "edition": "pro",
  "release_channel": "production",
  "license": { "code": "valid" },
  "limits": {
    "effective_human_cap": 100,
    "effective_team_member_cap": null,
    "write_brake_human_cap": 100
  },
  "features": { "audit_events": false, "model_runs": true, "observability": false },
  "support_tier": "standard",
  "term_end": "2027-06-16T00:00:00Z",
  "warning": null
}

Project Tools

Tool	Required scope	Purpose
list_projects	mcp:projects:read	Return visible non-deleted projects.
get_project	mcp:projects:read	Return one visible project.
create_project	mcp:projects:write	Create a project and owner membership.
update_project	mcp:projects:write	Update project fields and access.
delete_project	mcp:projects:write	Soft-delete a project.

Project reads follow each project’s status and read_access_mode. live projects use the configured read access mode. draft, test, and archived projects are visible only to admins and project owners. Project writes still require admin access or an owner row. resolve defaults to mode: "live". status: "test" projects can be used by resolve only with explicit project_id, mode: "test", and admin or project-owner access.

Participant Tools

Tool	Required scope	Purpose
list_participants	mcp:participants:read	Return visible non-deleted participants.
get_participant	mcp:participants:read	Return one visible participant.
search_directory_records	mcp:participants:read	Search cached directory users and groups.
list_participant_members	mcp:participants:read	List directory users/groups on a participant.
create_participant	mcp:participants:write	Create a participant in a manageable project.
update_participant	mcp:participants:write	Update participant fields, labels, metadata.
add_participant_member	mcp:participants:write	Add a directory user or group to a participant.
remove_participant_member	mcp:participants:write	Remove a directory user or group.
delete_participant	mcp:participants:write	Soft-delete a participant.

Resolve Request History Tools

Tool	Required scope	Purpose
list_resolve_requests	mcp:resolve-requests:read	Return compact visible resolve request history.
get_resolve_request	mcp:resolve-requests:read	Return one visible resolve request with detail.

Label Tools

Tool	Required scope	Purpose
list_labels	mcp:labels:read	Return labels and usage counts.
get_label	mcp:labels:read	Return one label.
create_label	mcp:labels:write	Create a label.
update_label	mcp:labels:write	Update label name or color.
delete_label	mcp:labels:write	Delete a label when allowed.

Label read tools require an active authenticated owner identity. Label mutation tools also require admin or effective project-owner authorization. Non-admin project owners can delete only labels they created, and only when every participant or resolve-request usage is in projects they own.

Delegation Tools

Tool	Required scope	Purpose
list_delegations	mcp:delegations:read	Return visible delegations.
get_delegation	mcp:delegations:read	Return one visible delegation.
create_delegation	mcp:delegations:write	Create a participant delegation.
update_delegation	mcp:delegations:write	Update a delegation.
revoke_delegation	mcp:delegations:write	Revoke a delegation.

Platform Administration Tools

These tools expose platform administration surfaces. The scope allows the MCP tool to be called, but the authenticated identity must still be an active platform admin. Scopes do not elevate the user’s platform role.

Tool	Required scope	Purpose
list_team_members	mcp:team-members:read	List platform team members.
get_team_member	mcp:team-members:read	Return one team member.
create_team_member	mcp:team-members:write	Create a team member.
update_team_member	mcp:team-members:write	Update a team member.
delete_team_member	mcp:team-members:write	Soft-delete a team member.
enable_team_member	mcp:team-members:write	Enable a team member.
disable_team_member	mcp:team-members:write	Disable a team member.
list_ai_agents	mcp:ai-agents:read	List AI agent identities.
get_ai_agent	mcp:ai-agents:read	Return one AI agent identity.
create_ai_agent	mcp:ai-agents:write	Create an AI agent identity.
update_ai_agent	mcp:ai-agents:write	Update an AI agent identity.
delete_ai_agent	mcp:ai-agents:write	Soft-delete an AI agent.
enable_ai_agent	mcp:ai-agents:write	Enable an AI agent.
disable_ai_agent	mcp:ai-agents:write	Disable an AI agent.
list_service_accounts	mcp:service-accounts:read	List service account identities.
get_service_account	mcp:service-accounts:read	Return one service account.
create_service_account	mcp:service-accounts:write	Create a service account.
update_service_account	mcp:service-accounts:write	Update a service account.
delete_service_account	mcp:service-accounts:write	Soft-delete a service account.
enable_service_account	mcp:service-accounts:write	Enable a service account.
disable_service_account	mcp:service-accounts:write	Disable a service account.
list_api_keys	mcp:api-keys:read	List API keys without secrets.
get_api_key	mcp:api-keys:read	Return one API key.
create_api_key	mcp:api-keys:write	Create an API key.
revoke_api_key	mcp:api-keys:write	Revoke an API key.
list_provider_connectors	mcp:provider-connectors:read	List provider connectors.
get_provider_connector	mcp:provider-connectors:read	Return one provider connector.
create_provider_connector	mcp:provider-connectors:write	Create a provider connector.
update_provider_connector	mcp:provider-connectors:write	Update a provider connector.
delete_provider_connector	mcp:provider-connectors:write	Delete a provider connector.
get_platform_settings	mcp:platform-settings:read	Return redacted platform settings.
update_platform_settings	mcp:platform-settings:write	Update platform settings.
get_observability_status	mcp:observability:read	Return sanitized runtime and OTLP delivery status.

Team member password inputs use password in the MCP payload. CLI users should pass the password through --password-stdin or --password-env so it does not enter shell history. Provider connector create/update payloads use the same strict snake_case JSON shape as REST. Provider connector update preserves omitted configuration and secret-reference fields. Platform settings update requires the wrapped shape { "settings": ... } and returns redacted settings.

Platform Observability Tools

Audit events, model runs, and observability status are read-only, admin-only, and license-gated. If the current product license does not include the feature, the tool returns a 403-style feature-unavailable error.

Tool	Required scope	Purpose
list_audit_events	mcp:audit-events:read	List audit events.
get_audit_event	mcp:audit-events:read	Return one audit event.
list_model_runs	mcp:model-runs:read	List model runs.
get_model_run	mcp:model-runs:read	Return one model run.
get_observability_status	mcp:observability:read	Return database, worker, runtime-instance, and OTLP delivery status.

get_observability_status is available in Enterprise. Its disabled, pending, healthy, or degraded status confirms only delivery to the configured OTLP endpoint, not downstream persistence. Endpoint credentials, headers, and complete paths are never returned.

List Tool Filters

List and search tools accept a limit from 1 to 100.

list_projects accepts:

{
  "query": "helios vendor",
  "limit": 10
}

query searches project name and description.

search_directory_records accepts:

{
  "query": "ethan wright",
  "type": "user",
  "limit": 10
}

type accepts all, user, or group. query searches cached directory record id, name, email, and description. This tool does not search upstream connectors live.

list_participant_members accepts:

{
  "participant_id": "part_...",
  "query": "ethan",
  "type": "user",
  "limit": 10
}

type accepts all, user, or group. The tool returns direct directory users and groups associated with the participant.

list_participants accepts optional filters:

{
  "query": "finance approvers",
  "limit": 10,
  "project_ids": ["proj_..."],
  "labels": ["Finance", "Vendor"],
  "metadata": [{ "key": "approval_limit_eur", "operator": "gte", "value": 75000 }]
}

Filter groups combine with AND semantics except project_ids, which uses OR semantics. Label matching is case-insensitive by name and exact by ID. Metadata keys must be snake_case. Ordered metadata operators support numeric and date-time metadata.

list_labels accepts:

{
  "query": "finance",
  "limit": 20
}

query searches label name.

list_delegations accepts:

{
  "status": "active",
  "scope": "participant",
  "project_id": "proj_...",
  "participant_id": "part_...",
  "delegator_user_id": "drec_...",
  "delegate_user_id": "drec_...",
  "limit": 25
}

status accepts active, expired, revoked, or upcoming. scope accepts all_participants or participant.

list_resolve_requests accepts:

{
  "project_id": "proj_...",
  "actor_id": "idn_...",
  "resolution_status": "success",
  "created_after": "2026-05-01T00:00:00Z",
  "created_before": "2026-06-01T00:00:00Z",
  "query": "Helios renewal",
  "limit": 25
}

resolution_status accepts success, not_found, out_of_scope, or error. actor_id is the Roster identity id of the authenticated requester who created the Resolve request, for example the user who signed in through OAuth or the identity behind a Roster API key. It is not a directory user id; directory users use drec_... ids in membership and delegation tools. Omit actor_id unless you are filtering history to a specific requester. query searches the original Resolve request text.

Participant reads follow the same project read access rules. Participant writes still require admin access or project ownership.