component.repair
Create a governed component-local repair proposal without mutating the baseline.
This record as markdown: /tools/visionmcp/component.repair.md
What component.repair does on Visionmcp
AI agents use component.repair 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 component.repair is rated Medium
This tool creates new repair proposals but explicitly preserves the baseline (no mutations to core data), making it a Write operation rather than Execute or Destructive. The 'governed' qualifier and local scope limit blast radius to medium severity — misuse would create unwanted proposals but not execute them or destroy existing data.
From the tool's definition Tool description states 'Create a governed component-local repair proposal' — the word 'Create' indicates data generation/modification. Crucially, it specifies 'without mutating the baseline,' meaning changes are reversible and scoped locally, not destructive.
Attacks that exploit this kind of access
The rule that runs component.repair 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 component.repair, this is the rule to start with:
component.repair 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 component.repair call is checked against it from then on.
Questions about component.repair
Create a governed component-local repair proposal without mutating the baseline. 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 component.repair: 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.
component.repair 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 component.repair 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 component.repair. 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.
component.repair 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