Create a new entity within a project.
AI agents use create_entity to create or update resources in TreeBeam MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your TreeBeam MCP Server environment.
This tool creates new data structures within the TreeBeam financial system. Creation is a Write operation—it modifies state but is not irreversible (deletion tools exist). It is not Financial because entity creation itself does not move money or commit financial obligations, though entities may be used in subsequent financial operations.
From the tool's definition Tool name 'create_entity' with description 'Create a new entity within a project' indicates data creation. In a financial management platform (TreeBeam), entities represent accounting objects (e.g., cost centers, departments, business units).
Attacks that exploit this kind of access
Create a new entity within a project. It is categorised as a Write tool in the TreeBeam MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the TreeBeam MCP Server MCP server in PolicyLayer and add a rule for create_entity: 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.
create_entity is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the create_entity 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 create_entity. 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.
create_entity 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 →