search_tasks
[SUPPORT] Read-only: Search tasks by keyword or natural-language query. Uses trigram similarity on Postgres, LIKE on SQLite. Returns top matches with similarity score.
This record as markdown: /tools/io-github-ajc3xc-meridian/search-tasks.md
What search_tasks does on Meridian
AI agents call search_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 | — | |
query | string | Yes | |
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 search_tasks is rated Low
This tool retrieves and queries data (task search results) with no side effects. The explicit 'Read-only' designation, combined with the search and return behavior, unambiguously places it in the Read category. Low severity because information disclosure through a task search has minimal blast radius in a typical AI coding session context.
From the tool's definition Tool description explicitly states 'Read-only: Search tasks by keyword or natural-language query' and returns matches with similarity scores; no modification, deletion, or execution capability described.
Attacks that exploit this kind of access
The rule that runs search_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 search_tasks, this is the rule to start with:
search_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 search_tasks call is checked against it from then on.
Questions about search_tasks
[SUPPORT] Read-only: Search tasks by keyword or natural-language query. Uses trigram similarity on Postgres, LIKE on SQLite. Returns top matches with similarity score. It is categorised as a Read tool in the Meridian MCP Server, which means it retrieves data without modifying state.
search_tasks accepts 4 parameters: limit, query, project_id, project_name. Required: query. 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 search_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.
search_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 search_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 search_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.
search_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