Diff the latest two versions of a model. Auto-resolves project + model when one of each exists.
AI agents call diff_latest_two to retrieve information from Bim Change Engine without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and analyzes existing BIM model versions to identify differences. It retrieves data and performs computations on that data (diff analysis) but does not create, modify, delete, or execute arbitrary operations.
From the tool's definition Tool performs diff analysis ('Diff the latest two versions') which retrieves and compares data between two versions. No modifications, deletions, or code execution are described.
Attacks that exploit this kind of access
Diff the latest two versions of a model. Auto-resolves project + model when one of each exists. It is categorised as a Read tool in the Bim Change Engine MCP Server, which means it retrieves data without modifying state.
Register the Bim Change Engine MCP server in PolicyLayer and add a rule for diff_latest_two: 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 Bim Change Engine. Nothing to install.
diff_latest_two 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 diff_latest_two 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 diff_latest_two. 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.
diff_latest_two is provided by the Bim Change Engine MCP server (rishibajaj-prodman/bim-change-engine). 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 →