PREFERRED for reviewing adjustments. Returns each adjustment with its line items pre-joined, including the resolved account name and account number on each line item. All data is returned in a single response with NO pagination. Use this tool whenever the user asks to see adjustments with their d...
AI agents call pivot_adjustments_by_adjustment 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 displays adjustment records with their associated line items and account details. There are no indications of data creation, modification, deletion, or execution of operations. It is a query/retrieval function that presents financial information for inspection. The requirement to provide a periodId is a filter parameter, not an action that modifies state.
From the tool's definition Tool description states it "Returns each adjustment with its line items pre-joined" and "All data is returned in a single response." The verb "Returns" and "review" indicate data retrieval with no modification.
Attacks that exploit this kind of access
PREFERRED for reviewing adjustments. Returns each adjustment with its line items pre-joined, including the resolved account name and account number on each line item. All data is returned in a single response with NO pagination. Use this tool whenever the user asks to see adjustments with their detail line items, or needs to review journal entries. 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_adjustment: 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_adjustment 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_adjustment 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_adjustment. 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_adjustment 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 →