Lists all thought files in the .project/thoughts/ directory structure. Shows available brain dump files organized by category.
AI agents call list_thoughts to retrieve information from Project MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a straightforward read operation that queries and enumerates existing thought files from a directory structure. It has no ability to create, modify, delete, or execute anything. The blast radius of misuse is negligible since an agent can only view metadata about thoughts, not expose sensitive content at scale or cause damage.
From the tool's definition Tool description explicitly states it 'Lists all thought files' and 'Shows available brain dump files' — pure data retrieval with no modification or side effects.
Documented attack patterns abuse exactly the kind of access list_thoughts gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Project MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for list_thoughts:
{
"version": "1",
"default": "deny",
"tools": {
"list_thoughts": {}
}
} list_thoughts 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.
Lists all thought files in the .project/thoughts/ directory structure. Shows available brain dump files organized by category. It is categorised as a Read tool in the Project MCP MCP Server, which means it retrieves data without modifying state.
Register the Project MCP server in PolicyLayer and add a rule for list_thoughts: 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 Project MCP. Nothing to install.
list_thoughts 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_thoughts 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_thoughts. 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_thoughts is provided by the Project MCP server (pouyanafisi/project-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Project MCP, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
42 Project MCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.