PREFERRED for analyzing adjustment impact by account. Returns one row per impacted account with the sum of adjustment line item amounts and count of distinct adjustments, for each requested period. Only accounts that have adjustment activity are included. All data is returned in a single response...
AI agents call pivot_adjustments_by_account 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 analyzes existing adjustment data by pivoting/grouping results. There are no side effects—no accounts, adjustments, or line items are created, modified, or deleted. The tool accepts parameters (periodId) that scope the query but cannot cause destructive or financial operations.
From the tool's definition The tool 'pivot_adjustments_by_account' returns aggregated data (sum of amounts, count of adjustments) filtered by account and period.
Attacks that exploit this kind of access
PREFERRED for analyzing adjustment impact by account. Returns one row per impacted account with the sum of adjustment line item amounts and count of distinct adjustments, for each requested period. Only accounts that have adjustment activity are included. All data is returned in a single response with NO pagination. Use this tool whenever the user asks which accounts were adjusted, or how much adjustment activity hit a particular account. 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: 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 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 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. 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 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 →