vision.search.versions

Build a version/variant/source-format lineage graph.

SERVERVisionmcp SOURCEjoshuahickscorp/visionmcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/visionmcp/vision.search.versions.md

WHAT IT DOES

What vision.search.versions does on Visionmcp

AI agents call vision.search.versions 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.

RISK

Why vision.search.versions is rated Low

The tool builds a lineage graph of versions, variants, and source formats. This is a read/query operation that retrieves and organizes existing version metadata without modifying, creating, or deleting data. Severity is low as misuse would only expose version history information.

From the tool's definition "Build a version/variant/source-format lineage graph" — constructs/retrieves a lineage graph, implying a read/query operation with no side effects

Attacks that exploit this kind of access

RECOMMENDED RULE

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

vision.search.versions Allowed

vision.search.versions is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "vision.search.versions": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about vision.search.versions

What does the vision.search.versions tool do? +

Build a version/variant/source-format lineage graph. It is categorised as a Read tool in the Visionmcp MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on vision.search.versions? +

Register the Vision MCP server in PolicyLayer and add a rule for vision.search.versions: 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 vision.search.versions? +

vision.search.versions is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit vision.search.versions? +

Yes. Add a rate_limit block to the vision.search.versions 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 vision.search.versions completely? +

Set action: deny in the PolicyLayer policy for vision.search.versions. 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 vision.search.versions? +

vision.search.versions 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

Roll out MCP under one policy →Data exfiltration →MCP token cost →