list_active_worktrees
[SUPPORT] dffcde86 — Read-only: list active (not-removed) git worktrees registered for a project, newest first, each row including the owning session's name. Reads the same active_worktrees registry the merge guard (validate_worktree_merge) and the REST worktree endpoints (GET /projects/{id}/work...
This record as markdown: /tools/io-github-ajc3xc-meridian/list-active-worktrees.md
What list_active_worktrees does on Meridian
AI agents call list_active_worktrees 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 |
|---|---|---|---|
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 list_active_worktrees is rated Low
Even though list_active_worktrees 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_active_worktrees 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_active_worktrees, this is the rule to start with:
list_active_worktrees 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_active_worktrees call is checked against it from then on.
Questions about list_active_worktrees
[SUPPORT] dffcde86 — Read-only: list active (not-removed) git worktrees registered for a project, newest first, each row including the owning session's name. Reads the same active_worktrees registry the merge guard (validate_worktree_merge) and the REST worktree endpoints (GET /projects/{id}/worktrees) use — this is the MCP-side view of it, for a session that wants to check what's checked out before creating a new worktree or investigating a stale one, without going through the REST API. Works identically on hosted and self-hosted Meridian: it only reads DB rows, never the filesystem. It is categorised as a Read tool in the Meridian MCP Server, which means it retrieves data without modifying state.
list_active_worktrees accepts 2 parameters: 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 list_active_worktrees: 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_active_worktrees 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_active_worktrees 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_active_worktrees. 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_active_worktrees 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