Get a single account group by ID within a project.
AI agents call get_account_group 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 financial data (account group information) from the TreeBeam accounting platform by ID. The operation is read-only with no side effects, making it a Read category tool. Severity is low because unauthorized access to account group metadata poses minimal risk compared to write, execute, or destructive operations, though the financial domain warrants baseline awareness.
From the tool's definition Tool name 'get_account_group' and description 'Get a single account group by ID' indicate a retrieval operation with no data modification or deletion.
Attacks that exploit this kind of access
Get a single account group by ID within a project. 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 get_account_group: 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.
get_account_group 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 get_account_group 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 get_account_group. 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.
get_account_group 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 →