validation.plan_locality
Plan only affected views, passes, regions, and metrics for a semantic change.
This record as markdown: /tools/visionmcp/validation.plan-locality.md
What validation.plan_locality does on Visionmcp
AI agents call validation.plan_locality to retrieve information from Visionmcp without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why validation.plan_locality is rated Low
This is a read-only tool that analyzes and reports which components would be affected by a change, supporting the 'evidence-first' compiler approach described in the server. It gathers information to inform decisions but does not implement changes, delete data, or trigger external operations. The blast radius of misuse is minimal since it only returns planning information.
From the tool's definition The tool 'plan_locality' with description 'Plan only affected views, passes, regions, and metrics for a semantic change' performs analysis and planning without executing modifications.
Attacks that exploit this kind of access
The rule that runs validation.plan_locality 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 validation.plan_locality, this is the rule to start with:
validation.plan_locality is read-only, so it stays allowed. 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 validation.plan_locality call is checked against it from then on.
Questions about validation.plan_locality
Plan only affected views, passes, regions, and metrics for a semantic change. It is categorised as a Read tool in the Visionmcp MCP Server, which means it retrieves data without modifying state.
Register the Vision MCP server in PolicyLayer and add a rule for validation.plan_locality: 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.
validation.plan_locality 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 validation.plan_locality 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 validation.plan_locality. 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.
validation.plan_locality 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