AI agents call list_recent_tool to retrieve information from Brain without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
List operations are non-destructive queries that retrieve data without side effects. The absence of a description lowers confidence slightly, but the naming convention and the read-heavy nature of this note-taking system support classification as a Read tool with low severity.
From the tool's definition Tool name 'list_recent_tool' indicates a listing/retrieval operation. No description provided, but context from sibling tools (read_note_tool, hybrid_search_tool, keyword_search_tool, semantic_search_tool) suggests this server is designed for querying and…
Documented attack patterns abuse exactly the kind of access list_recent_tool gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Brain, and nothing reaches the server without passing your rules. This is the rule we recommend for list_recent_tool:
{
"version": "1",
"default": "deny",
"tools": {
"list_recent_tool": {}
}
}list_recent_tool 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_recent_tool. It is categorised as a Read tool in the Brain MCP Server, which means it retrieves data without modifying state.
Register the Brain MCP server in PolicyLayer and add a rule for list_recent_tool: 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 Brain. Nothing to install.
list_recent_tool 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_recent_tool 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_recent_tool. 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_recent_tool is provided by the Brain MCP server (irahulstomar/brain-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Brain, 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.
10 Brain tools catalogued and risk-classified — across an index of 43,000+ MCP servers.