vision.measure_visual_parity
Run governed pixel, perceptual, layout, typography, crop, stacking, and distribution metrics.
This record as markdown: /tools/visionmcp/vision.measure-visual-parity.md
What vision.measure_visual_parity does on Visionmcp
AI agents invoke vision.measure_visual_parity to trigger actions in Visionmcp. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
Why vision.measure_visual_parity is rated High
This tool executes a governed measurement process with measurable outputs rather than simply reading static data. While it does not modify data (Write) or delete anything (Destructive), it triggers computation with side effects determinable by context (which metrics to measure, on which visual artifacts).
From the tool's definition Tool description states it 'run[s]' metrics across multiple visual dimensions (pixel, perceptual, layout, typography, crop, stacking, distribution). The verb 'run' indicates active computation/measurement execution rather than passive data retrieval.
Attacks that exploit this kind of access
The rule that runs vision.measure_visual_parity 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 vision.measure_visual_parity, this is the rule to start with:
vision.measure_visual_parity stays usable, but rate-capped: a runaway agent can't fire it dozens of times 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 vision.measure_visual_parity call is checked against it from then on.
Questions about vision.measure_visual_parity
Run governed pixel, perceptual, layout, typography, crop, stacking, and distribution metrics. It is categorised as a Execute tool in the Visionmcp MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Vision MCP server in PolicyLayer and add a rule for vision.measure_visual_parity: 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.
vision.measure_visual_parity is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the vision.measure_visual_parity 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 vision.measure_visual_parity. 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.
vision.measure_visual_parity 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.
Across the catalogue