Search/list entities within a project. Supports filtering — see server instructions for filter syntax. Results are paginated — if a continuationToken is returned, pass it in the next call to retrieve more.
AI agents call search_entities to retrieve information from TreeBeam MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and queries entity data with no side effects. It is a standard read operation that returns paginated search results. While the TreeBeam platform handles financial data, this particular tool only performs lookups and does not move money, create obligations, or modify state. The low severity reflects that reading entity lists poses minimal risk even if misused by an agent.
From the tool's definition Tool description states 'Search/list entities within a project' and mentions 'filtering' and 'pagination' for retrieval. No modification, deletion, or execution capability is described.
Attacks that exploit this kind of access
Search/list entities within a project. Supports filtering — see server instructions for filter syntax. Results are paginated — if a continuationToken is returned, pass it in the next call to retrieve more. It is categorised as a Read tool in the TreeBeam MCP Server MCP Server, which means it retrieves data without modifying state.
Register the TreeBeam MCP Server MCP server in PolicyLayer and add a rule for search_entities: 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 TreeBeam MCP Server. Nothing to install.
search_entities 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 search_entities 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 search_entities. 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.
search_entities is provided by the TreeBeam MCP Server MCP server (treebeam-code/tb-mcpserver). 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 →