PREFERRED for analyzing adjustment impact by account group. Returns one row per impacted account group with summed adjustment amounts and distinct adjustment counts, for each requested period. Only account groups that have adjustment activity are included. All data is returned in a single respons...
AI agents call pivot_adjustments_by_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 is a query/analytical tool that aggregates and returns financial data from the TreeBeam platform grouped by account group and period. While the data is financial in nature, the tool itself performs no financial transactions, modifications, or irreversible operations—it simply reads and presents existing adjustment data in a summarized format.
From the tool's definition The tool description states it "Returns one row per impacted account group with summed adjustment amounts and distinct adjustment counts" and "All data is returned in a single response with NO pagination." The verb "Returns" and "analyzing" indicate data…
Attacks that exploit this kind of access
PREFERRED for analyzing adjustment impact by account group. Returns one row per impacted account group with summed adjustment amounts and distinct adjustment counts, for each requested period. Only account groups that have adjustment activity are included. All data is returned in a single response with NO pagination. Use this tool whenever the user asks about adjustment totals grouped by account group. You must provide at least one periodId — use search_periods first to find period IDs if needed. 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 pivot_adjustments_by_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.
pivot_adjustments_by_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 pivot_adjustments_by_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 pivot_adjustments_by_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.
pivot_adjustments_by_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.
pivot_adjustments_by_account_group is one line of TreeBeam MCP Server's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →