Search your second brain by text, category, or tag.
AI agents call brain_search to retrieve information from Claude Team MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool only queries and retrieves data from an internal knowledge store ('second brain'). It has no side effects, does not modify or delete data, does not execute code or external operations, and does not involve financial transactions. It is a straightforward search/query function, which is the canonical Read category.
From the tool's definition Tool name 'brain_search' and description explicitly states it 'search[es] your second brain by text, category, or tag' — a pure retrieval operation with no modification, deletion, or execution of external systems.
Attacks that exploit this kind of access
Search your second brain by text, category, or tag. It is categorised as a Read tool in the Claude Team MCP MCP Server, which means it retrieves data without modifying state.
Register the Claude Team MCP server in PolicyLayer and add a rule for brain_search: 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 Team MCP. Nothing to install.
brain_search 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 brain_search 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 brain_search. 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.
brain_search is provided by the Claude Team MCP server (lakshan12367/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →