get_tasks
[SUPPORT] Read-only: Get recent tasks across all sessions.
This record as markdown: /tools/io-github-ajc3xc-meridian/get-tasks.md
What get_tasks does on Meridian
AI agents call get_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 | — | |
project_name | string | — | Project name — an alternative to project_id; resolved to the id internally. project_id wins if both are given. |
Parameters from the server's own tool schema.
Why get_tasks is rated Low
This tool retrieves task data without modifying, deleting, or executing any operations. It has minimal blast radius—an AI agent misusing it can only access task information it may not be authorized for, but cannot alter state or trigger external actions. The explicit 'Read-only' marker and retrieval-focused verb ('Get') place it firmly in the Read category.
From the tool's definition Tool name 'get_tasks' and description explicitly states 'Read-only: Get recent tasks across all sessions.' The 'Read-only' designation and verb 'Get' confirm this is a retrieval operation with no side effects.
Attacks that exploit this kind of access
The rule that runs get_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 get_tasks, this is the rule to start with:
get_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 get_tasks call is checked against it from then on.
Questions about get_tasks
[SUPPORT] Read-only: Get recent tasks across all sessions. It is categorised as a Read tool in the Meridian MCP Server, which means it retrieves data without modifying state.
get_tasks accepts 3 parameters: limit, project_id, project_name. 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 get_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.
get_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 get_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 get_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.
get_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