list_projects
[MAINTENANCE] Read-only: List all projects — find, browse, or look up your projects and their IDs. Call this first when you have a project name but need its project_id, or to discover which projects exist. Returns [{id, name, sprint, created_at}] newest first.
This record as markdown: /tools/io-github-ajc3xc-meridian/list-projects.md
What list_projects does on Meridian
AI agents call list_projects 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.
Why list_projects is rated Low
This is a pure data retrieval operation with no write, delete, execute, or financial capabilities. Misuse (e.g., an agent listing all projects) poses minimal risk — at worst information disclosure of project names and IDs already accessible to the authenticated user. Severity is low because the blast radius of accidental misuse is negligible.
From the tool's definition Tool is explicitly marked [MAINTENANCE] Read-only and returns project metadata ({id, name, sprint, created_at}). The description states it lists, finds, browses, and looks up projects with no side effects.
Attacks that exploit this kind of access
The rule that runs list_projects 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_projects, this is the rule to start with:
list_projects 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_projects call is checked against it from then on.
Questions about list_projects
[MAINTENANCE] Read-only: List all projects — find, browse, or look up your projects and their IDs. Call this first when you have a project name but need its project_id, or to discover which projects exist. Returns [{id, name, sprint, created_at}] newest first. It is categorised as a Read tool in the Meridian MCP Server, which means it retrieves data without modifying state.
Register the Meridian MCP server in PolicyLayer and add a rule for list_projects: 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_projects 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_projects 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_projects. 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_projects 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