vision.create_benchmark
Package a licensed source-known benchmark with explicit source isolation.
This record as markdown: /tools/visionmcp/vision.create-benchmark.md
What vision.create_benchmark does on Visionmcp
AI agents use vision.create_benchmark 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 vision.create_benchmark is rated Medium
The tool creates/packages a benchmark dataset or artifact, which is a reversible write operation. There is no indication of code execution, deletion, or financial transactions. Severity is medium because packaging benchmark data with source isolation could affect model training pipelines if misused, but the operation appears to be a creation/write action rather than destructive or executable.
From the tool's definition 'Package a licensed source-known benchmark with explicit source isolation' — creates a new benchmark artifact
Attacks that exploit this kind of access
The rule that runs vision.create_benchmark 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.create_benchmark, this is the rule to start with:
vision.create_benchmark 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 vision.create_benchmark call is checked against it from then on.
Questions about vision.create_benchmark
Package a licensed source-known benchmark with explicit source isolation. 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 vision.create_benchmark: 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.
vision.create_benchmark 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 vision.create_benchmark 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 vision.create_benchmark. 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.
vision.create_benchmark 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