search_all
[SUPPORT] Read-only: Universal search across all project content: tasks, notes, pinned decisions, and sprint items. Uses LIKE matching (SQLite) or ILIKE (Postgres). Returns grouped results: {tasks, notes, decisions, sprint_items, total, cursor, limit, has_more, next_cursor}. limit (default 10, cl...
This record as markdown: /tools/io-github-ajc3xc-meridian/search-all.md
What search_all does on Meridian
AI agents call search_all 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 | — | Max results per type (default 10, clamped 1..100). |
query | string | Yes | |
cursor | integer | — | Offset applied to all four result lists (default 0). Pass a prior response's next_cursor to fetch the next page. |
expand | boolean | — | Default false: collapse parent_id/item_group clusters in sprint_items into one summary row each. Pass true for the full ungrouped list. |
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_all is rated Low
Even though search_all 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.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
The rule that runs search_all 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_all, this is the rule to start with:
search_all 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_all call is checked against it from then on.
Questions about search_all
[SUPPORT] Read-only: Universal search across all project content: tasks, notes, pinned decisions, and sprint items. Uses LIKE matching (SQLite) or ILIKE (Postgres). Returns grouped results: {tasks, notes, decisions, sprint_items, total, cursor, limit, has_more, next_cursor}. limit (default 10, clamped 1..100) and cursor (default 0) bound and page each of the four lists with one shared offset (W1-A) — pass a prior response's next_cursor back in as cursor to fetch the next page; has_more is a per-list bool so you can tell exactly which list(s) still have more. sprint_items default-collapse any parent_id/item_group cluster (2+ items) into one summary row — pass expand=true for the full ungrouped list. It is categorised as a Read tool in the Meridian MCP Server, which means it retrieves data without modifying state.
search_all accepts 6 parameters: limit, query, cursor, expand, 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_all: 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_all 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_all 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_all. 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_all 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