Open EPM ← Back to openepm.dev

read_v2_task

Returns the authorized task, its native status and bounded event page. Check interruptible and rerunSupported before invoking a control, and keep the native source ID when reconciling evidence.

These signatures come from local MCP tool discovery. Use the signature registered by your deployment and confirm your identity and permissions before calling the tool.

Endpoint signatures and example arguments

Examples show the arguments to the tool. Replace placeholder IDs and illustrative revisions with values from your authorized disposable scope.

Bound application

Read one authorized task and its bounded immutable event page.

Required arguments
task_id
Optional arguments
after_event, event_limit
{
  "task_id": "{{task_id}}",
  "after_event": 0,
  "event_limit": 25
}
Exact JSON input schema
{
  "properties": {
    "task_id": {
      "title": "Task Id",
      "type": "string"
    },
    "after_event": {
      "default": 0,
      "title": "After Event",
      "type": "integer"
    },
    "event_limit": {
      "default": 100,
      "title": "Event Limit",
      "type": "integer"
    }
  },
  "required": [
    "task_id"
  ],
  "title": "read_v2_taskArguments",
  "type": "object"
}

Application router

Read one authorized task and its bounded immutable event page.

Required arguments
workspace_id, application_id, task_id
Optional arguments
after_event, event_limit
{
  "workspace_id": "{{workspace_id}}",
  "application_id": "operating-cube",
  "task_id": "{{task_id}}",
  "after_event": 0,
  "event_limit": 25
}
Exact JSON input schema
{
  "properties": {
    "workspace_id": {
      "title": "Workspace Id",
      "type": "string"
    },
    "application_id": {
      "title": "Application Id",
      "type": "string"
    },
    "task_id": {
      "title": "Task Id",
      "type": "string"
    },
    "after_event": {
      "default": 0,
      "title": "After Event",
      "type": "integer"
    },
    "event_limit": {
      "default": 100,
      "title": "Event Limit",
      "type": "integer"
    }
  },
  "required": [
    "workspace_id",
    "application_id",
    "task_id"
  ],
  "title": "read_v2_taskArguments",
  "type": "object"
}

Handling errors

MCP_TOOL_CAPACITY_NOT_DISPATCHED means the server did not dispatch this call. MCP_TOOL_DEADLINE_OUTCOME_UNKNOWN or MCP_TOOL_PROCESS_FAILED_OUTCOME_UNKNOWN leaves the outcome unknown. For a call with effects, reconcile the original request before starting a new one. For a scoped denial, verify the caller's grant and the selected target.

Module guidelines Β· Related workflow Β· Application-language function catalog

Discussion

Discussing read_v2_task

The discussion service requires JavaScript and a connection to Firebase.