evidence.propose_legacy_reference_adoption

Propose artifact-bound migration of legacy references without inferring rights.

SERVERVisionmcp SOURCEjoshuahickscorp/visionmcp

Medium RISK CLASS

Category Write

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/visionmcp/evidence.propose-legacy-reference-adoption.md

WHAT IT DOES

What evidence.propose_legacy_reference_adoption does on Visionmcp

AI agents use evidence.propose_legacy_reference_adoption 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.

RISK

Why evidence.propose_legacy_reference_adoption is rated Medium

The tool proposes a migration of legacy references, which is a write-like operation creating or modifying data (proposals/migration records). It does not delete or execute code, and 'without inferring rights' suggests it is bounded in scope. Severity is medium because a misconfigured migration proposal could affect reference bindings, but it is reversible at proposal stage.

From the tool's definition Propose artifact-bound migration of legacy references without inferring rights

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs evidence.propose_legacy_reference_adoption 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 evidence.propose_legacy_reference_adoption, this is the rule to start with:

evidence.propose_legacy_reference_adoption Rate-limited

evidence.propose_legacy_reference_adoption 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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "evidence.propose_legacy_reference_adoption": {
      "limits": [
        {
          "counter": "evidence.propose_legacy_reference_adoption_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Visionmcp, apply this rule, and every evidence.propose_legacy_reference_adoption call is checked against it from then on.

FAQ

Questions about evidence.propose_legacy_reference_adoption

What does the evidence.propose_legacy_reference_adoption tool do? +

Propose artifact-bound migration of legacy references without inferring rights. 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.

How do I enforce a policy on evidence.propose_legacy_reference_adoption? +

Register the Vision MCP server in PolicyLayer and add a rule for evidence.propose_legacy_reference_adoption: 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.

What risk level is evidence.propose_legacy_reference_adoption? +

evidence.propose_legacy_reference_adoption is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit evidence.propose_legacy_reference_adoption? +

Yes. Add a rate_limit block to the evidence.propose_legacy_reference_adoption 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.

How do I block evidence.propose_legacy_reference_adoption completely? +

Set action: deny in the PolicyLayer policy for evidence.propose_legacy_reference_adoption. 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.

What MCP server provides evidence.propose_legacy_reference_adoption? +

evidence.propose_legacy_reference_adoption 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.

KEEP EXPLORING

More on Vision, and thousands of servers like it.

This server

All 376 Vision tools →

Across the catalogue

The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →