Run and monitor meters with Mediation MCP

Use this reference to start, stop, monitor, and analyze Mediation meter runs and prefetch operations.

The manage_meters_run tool manages the meter run lifecycle. It provides 14 operations for starting and stopping runs, checking status and history, reviewing results, refreshing prefetch data, and ingesting usage events. Start with run_guidance to retrieve workflows and tips. Obtain approval before you execute a write operation.

manage_meters_run operations

Operation	Access	Purpose
`run_guidance`	Read	Retrieve run workflows and tips. Start here.
`run_meter`	Write	Start a run in `NORMAL` or `DEBUG` mode.
`stop_meter_run`	Write	Stop a run. Prefer the `runId` from the start response.
`get_run_status`	Read	Retrieve the current status for a meter and version.
`list_run_history`	Read	List run history with filters and pagination.
`get_run_summary`	Read	Retrieve per-operator counts. Requires `runHistoryId`.
`get_run_records`	Read	Retrieve paginated SINK output. Requires `runHistoryId` and a SINK `taskId`.
`get_operator_summary`	Read	Retrieve aggregates for a time window.
`query_event_store`	Read	Run an asynchronous SQL SELECT. Poll for results according to your build.
`list_prefetch_definitions`	Read/write	List prefetch definitions.
`get_prefetch_status`	Read/write	Retrieve the status of a prefetch operation.
`start_prefetch`	Read/write	Start a prefetch operation. You can optionally specify a processor ID.
`cancel_prefetch`	Read/write	Cancel a prefetch operation.
`ingest_usage_events`	Write	Return a REST URL that the caller uses to post usage events with OAuth.

Run statuses

A meter run can have one of the following statuses:

NEVER_RUN
INITIALIZING
RUNNING
STOPPING
PAUSED
COMPLETED
FAILED
CANCELED
JOB_SUBMISSION_IN_PROGRESS
FORCE_STOPPED

Stop behavior

A graceful stop is the default. When supported, a force stop can drop streaming data that is in flight. A force stop is not available when the run status is already STOPPING.