clear_calibration
Delete all stored calibration data (Cal,clear). pH/ORP/DO/EC/RTD return to uncalibrated;
This record as markdown: /tools/lab-instrument-mcps/clear-calibration.md
What clear_calibration does on Pypi:labmcp Alicat
AI agents call clear_calibration to permanently remove resources in Pypi:labmcp Alicat, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why clear_calibration is rated Critical
Irreversibly removes calibration data essential for instrument accuracy; cannot be easily recovered without recalibration.
From the tool's definition Delete all stored calibration data; pH/ORP/DO/EC/RTD return to uncalibrated.
Attacks that exploit this kind of access
The rule that runs clear_calibration safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Pypi:labmcp Alicat, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For clear_calibration, this is the rule to start with:
clear_calibration 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 Pypi:labmcp Alicat, apply this rule, and every clear_calibration call is checked against it from then on.
Questions about clear_calibration
Delete all stored calibration data (Cal,clear). pH/ORP/DO/EC/RTD return to uncalibrated;. It is categorised as a Destructive tool in the Pypi:labmcp Alicat MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Pypi:labmcp Alicat MCP server in PolicyLayer and add a rule for clear_calibration: 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 Pypi:labmcp Alicat. Nothing to install.
clear_calibration 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 clear_calibration 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 clear_calibration. 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.
clear_calibration is provided by the Pypi:labmcp Alicat MCP server (pypi:labmcp-alicat). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Pypi:labmcp Alicat, and thousands of servers like it.
Across the catalogue