This record as markdown: /tools/app-businys-mcp-server/delete-measurement.md
What delete_measurement does on Businys
AI agents call delete_measurement to permanently remove resources in Businys, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why delete_measurement is rated Critical
This tool performs an irreversible deletion operation on measurement entries. Even though the blast radius is limited to a single measurement record rather than bulk data, deletion cannot be undone without external recovery mechanisms. This qualifies as Destructive rather than Write (which covers reversible modifications).
From the tool's definition Tool name is 'delete_measurement' and description states 'Delete a measurement entry.' The verb 'delete' explicitly indicates irreversible removal of data.
Attacks that exploit this kind of access
The rule that runs delete_measurement safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Businys, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For delete_measurement, this is the rule to start with:
delete_measurement is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Businys, apply this rule, and every delete_measurement call is checked against it from then on.
Questions about delete_measurement
Delete a measurement entry. It is categorised as a Destructive tool in the Businys MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Businys MCP server in PolicyLayer and add a rule for delete_measurement: 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 Businys. Nothing to install.
delete_measurement is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the delete_measurement 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 delete_measurement. 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.
delete_measurement is provided by the Businys MCP server (@businys/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Businys, and thousands of servers like it.
Across the catalogue