list_projects

THE RISK

Low Risk

Why list_projects needs a policy

This tool performs a read-only operation that retrieves metadata about available projects. There are no side effects, no data modification, no code execution, and no destructive or financial operations. It is a simple enumeration/discovery tool, making it a Read category with low severity since it only exposes project names/identifiers without executing actions or modifying state.

From the tool's definition Tool name is 'list_projects' and description states it 'List all projects with Claude Code conversation history'. The verb 'list' and the action of retrieving/enumerating available projects indicates data retrieval without modification or execution.

Documented attack patterns abuse exactly the kind of access list_projects gives an agent:

POLICY

How to control list_projects

PolicyLayer is an MCP gateway — it sits between your AI agents and Claude Code History MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for list_projects:

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "list_projects": {}
  }
}

list_projects is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

Create a free account and register Claude Code History MCP Server — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

CAP THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Claude Code History MCP Server tools

Read get_conversation_history Get paginated conversation history (use after exploring with list_projects/list_sessions f Read list_sessions List conversation sessions for a project or date range (use after list_projects to find sp Read search_conversations Search through conversation history by content (useful for finding specific topics across

All 4 Claude Code History MCP Server tools →

Read tools on other servers

M-Team MCP Server get_torrent_detail YouTube MCP Server search_channel Android Forensics ADB MCP Server parse_browser_history 0xarchive web3_challenge

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Data exfiltration → How read access becomes an exfiltration channel when chained with untrusted content.
MCP token cost → What connecting this server costs in context-window tokens on every request.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about list_projects

What does the list_projects tool do? +

List all projects with Claude Code conversation history (start here to explore available data). It is categorised as a Read tool in the Claude Code History MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on list_projects? +

Register the Claude Code History MCP Server 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 Claude Code History MCP Server. Nothing to install.

What risk level is list_projects? +

list_projects is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit list_projects? +

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.

How do I block list_projects completely? +

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.

What MCP server provides list_projects? +

list_projects is provided by the Claude Code History MCP Server MCP server (yudppp/claude-code-history-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Claude Code History MCP Server tool call.

Start from Claude Code History MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →