measurement.add_physical
Register calibrated physical inputs while retaining uncertainty and calibration.
This record as markdown: /tools/visionmcp/measurement.add-physical.md
What measurement.add_physical does on Visionmcp
AI agents use measurement.add_physical to create or update resources in Visionmcp, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Visionmcp environment.
Why measurement.add_physical is rated Medium
The tool creates/registers new measurement data in the system (a write operation). It does not appear to execute code or delete data. The severity is medium because miscalibrated or incorrect physical measurements could propagate errors through downstream analysis or model training pipelines, but the action itself is reversible in principle.
From the tool's definition "Register calibrated physical inputs" — registers/adds new data entries with calibration and uncertainty metadata
Attacks that exploit this kind of access
The rule that runs measurement.add_physical safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Visionmcp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For measurement.add_physical, this is the rule to start with:
measurement.add_physical stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Visionmcp, apply this rule, and every measurement.add_physical call is checked against it from then on.
Questions about measurement.add_physical
Register calibrated physical inputs while retaining uncertainty and calibration. It is categorised as a Write tool in the Visionmcp MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Vision MCP server in PolicyLayer and add a rule for measurement.add_physical: 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 Visionmcp. Nothing to install.
measurement.add_physical 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 measurement.add_physical 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 measurement.add_physical. 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.
measurement.add_physical is provided by the Vision MCP server (joshuahickscorp/visionmcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Vision, and thousands of servers like it.
This server
Across the catalogue