Search/list raw account group records within a project. Supports filtering — see server instructions for filter syntax. Use this tool to look up a specific subset of account groups by type. DO NOT use this tool to build financial summaries by account group — use the pivot_trial_balance_by_account...
AI agents call search_account_groups 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 account group data from TreeBeam's financial management platform without side effects. It supports filtering and pagination for querying existing records but does not create, modify, delete, or execute operations. This is a classic Read operation with minimal blast radius—an AI misuse would result in unauthorized data access rather than data loss or financial harm.
From the tool's definition Tool description explicitly states "Search/list raw account group records" and "retrieve more" results via pagination. No creation, modification, deletion, or execution of commands is performed. The tool only queries and returns data.
Attacks that exploit this kind of access
Search/list raw account group records within a project. Supports filtering — see server instructions for filter syntax. Use this tool to look up a specific subset of account groups by type. DO NOT use this tool to build financial summaries by account group — use the pivot_trial_balance_by_account_group or pivot_trial_balance_by_fs_group tools instead, which return pre-aggregated totals in a single response with no pagination. 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_account_groups: 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_account_groups 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_account_groups 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_account_groups. 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_account_groups 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 →