list_remote_tasks
[SUPPORT] 32d3d5de — Read the project's persisted remote-task register (last-known status only — no live SSH check is made; call get_remote_task_status for that). By default terminal jobs are omitted so a new/resumed session sees only work that may still need checking on.
This record as markdown: /tools/io-github-ajc3xc-meridian/list-remote-tasks.md
What list_remote_tasks does on Meridian
AI agents call list_remote_tasks to retrieve information from Meridian without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
limit | integer | — | |
project_id | string | — | |
session_id | string | — | Optional: restrict to jobs started by this session. |
project_name | string | — | Project name — an alternative to project_id; resolved to the id internally. project_id wins if both are given. |
include_terminal | boolean | — |
Parameters from the server's own tool schema.
Why list_remote_tasks is rated Low
Even though list_remote_tasks only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
Attacks that exploit this kind of access
The rule that runs list_remote_tasks safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Meridian, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For list_remote_tasks, this is the rule to start with:
list_remote_tasks is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Meridian, apply this rule, and every list_remote_tasks call is checked against it from then on.
Questions about list_remote_tasks
[SUPPORT] 32d3d5de — Read the project's persisted remote-task register (last-known status only — no live SSH check is made; call get_remote_task_status for that). By default terminal jobs are omitted so a new/resumed session sees only work that may still need checking on. It is categorised as a Read tool in the Meridian MCP Server, which means it retrieves data without modifying state.
list_remote_tasks accepts 5 parameters: limit, project_id, session_id, project_name, include_terminal. The full parameter table on this page comes from the server's own tool schema.
Register the Meridian MCP server in PolicyLayer and add a rule for list_remote_tasks: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches Meridian. Nothing to install.
list_remote_tasks is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the list_remote_tasks rule in your PolicyLayer policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.
Set action: deny in the PolicyLayer policy for list_remote_tasks. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.
list_remote_tasks is provided by the Meridian MCP server (@meridianmcp/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Meridian, and thousands of servers like it.
This server
Across the catalogue