Search/list raw adjustment records within a project. Supports filtering — see server instructions for filter syntax. Use this tool to look up a specific subset of adjustments by period, type, status, or other criteria. DO NOT use this tool to summarize or analyze adjustment data across periods or...
AI agents call search_adjustments 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 read-only operation that retrieves financial adjustment records from the TreeBeam accounting platform. While the data accessed (financial records) is sensitive, the tool itself performs no modifications, deletions, or financial transactions.
From the tool's definition Tool description explicitly states "Search/list raw adjustment records" and "look up a specific subset of adjustments". The tool retrieves and queries data with support for filtering and pagination, with no mention of creating, modifying, or deleting records.
Attacks that exploit this kind of access
Search/list raw adjustment records within a project. Supports filtering — see server instructions for filter syntax. Use this tool to look up a specific subset of adjustments by period, type, status, or other criteria. DO NOT use this tool to summarize or analyze adjustment data across periods or accounts — use the pivot_adjustments_* 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_adjustments: 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_adjustments 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_adjustments 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_adjustments. 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_adjustments 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 →