workflow.repair_existing_model
Create an evidence-bound repair proposal; authorization and review remain separate.
This record as markdown: /tools/visionmcp/workflow.repair-existing-model.md
What workflow.repair_existing_model does on Visionmcp
AI agents use workflow.repair_existing_model 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 workflow.repair_existing_model is rated Medium
The tool creates or proposes modifications to an existing model (reversible write operation). The phrase 'authorization and review remain separate' explicitly indicates this is a proposal-generation step, not an autonomous execution or destructive operation. While repairs could have downstream effects, the tool itself generates a proposal for human review, fitting the Write category.
From the tool's definition Tool name contains 'repair' and description states 'Create an evidence-bound repair proposal', indicating creation of a modification artifact rather than irreversible deletion or execution of external code.
Attacks that exploit this kind of access
The rule that runs workflow.repair_existing_model 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 workflow.repair_existing_model, this is the rule to start with:
workflow.repair_existing_model 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 workflow.repair_existing_model call is checked against it from then on.
Questions about workflow.repair_existing_model
Create an evidence-bound repair proposal; authorization and review remain separate. 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 workflow.repair_existing_model: 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.
workflow.repair_existing_model 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 workflow.repair_existing_model 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 workflow.repair_existing_model. 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.
workflow.repair_existing_model 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