List all projects with saved states
AI agents call list_active_projects to retrieve information from Claude Thread Continuity without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and displays information about existing projects without creating, modifying, deleting, or executing any operations. It is a query/list operation typical of Read category tools. The severity is low because listing projects poses minimal risk—it only exposes metadata about project names and their saved states, with no side effects or ability to affect system state.
From the tool's definition Tool name 'list_active_projects' and description 'List all projects with saved states' indicate a retrieval operation with no modification or execution of external operations.
Documented attack patterns abuse exactly the kind of access list_active_projects gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Claude Thread Continuity, and nothing reaches the server without passing your rules. This is the rule we recommend for list_active_projects:
{
"version": "1",
"default": "deny",
"tools": {
"list_active_projects": {}
}
}list_active_projects is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
List all projects with saved states. It is categorised as a Read tool in the Claude Thread Continuity MCP Server, which means it retrieves data without modifying state.
Register the Claude Thread Continuity MCP server in PolicyLayer and add a rule for list_active_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 Claude Thread Continuity. Nothing to install.
list_active_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_active_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_active_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_active_projects is provided by the Claude Thread Continuity MCP server (peless/claude-thread-continuity). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 6 Claude Thread Continuity tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
6 Claude Thread Continuity tools catalogued and risk-classified — across an index of 42,500+ MCP servers.