MCP

MCP tool reference

Reference for all 23 catalog, credential, diagnostic, probe, safety, and audit tools.

Diagnostic tools

ping_broker

Check authenticated broker connectivity.

list_services

List service heartbeats, SDKs, commits, capabilities, online state, and caveats.

get_safety_overview

Return per-service safety state, enforced limits, reason codes, and probe counts.

list_audit_events

Read tenant-scoped control events without bearer secrets or captured values.

Catalog tools

list_projects

List active or archived projects.

create_project

Create or restore a project identity.

archive_project

Archive a project and revoke affected active credentials.

list_environments

List deployment environments in a project.

create_environment

Create or restore a project environment.

archive_environment

Archive an environment and revoke its active credentials.

list_registered_services

List project-level service identities.

register_service

Register or restore a service identity in a project.

archive_service

Archive a service and revoke its credentials in all environments.

Credential tools

create_service_credential

Issue an environment-scoped runtime key and return plaintext once.

list_service_credentials

List credential IDs, labels, prefixes, dates, and revocation state.

revoke_service_credential

Immediately revoke one runtime credential.

Probe tools

set_snapshot_probe

Capture bounded locals, paths, expressions, stack locations, and optional per-frame locals.

set_log_probe

Emit temporary debug, info, warn, or error telemetry with safe placeholders.

set_counter_probe

Count source-line executions with runtime pre-aggregation.

set_metric_probe

Aggregate count, sum, min, max, and last for a numeric path or expression.

list_probes

Inspect probe definitions and latest runtime status.

get_probe_data

Read retained evidence or long-poll up to 30 seconds.

remove_probe

Delete a probe and uninstall it on the next agent poll.

Scope and approvals

Operational tools accept project_id and environment_id. Probe setters also require the target service_id, source file, one-based line, and user-supplied deployed commit_hash.

Archive, revoke, and remove operations are marked destructive. Probe setters alter diagnostic instrumentation but are not marked destructive because they do not intentionally mutate application variables.