reference.import
Queue immutable reference ingestion with metadata and quality inspection.
This record as markdown: /tools/visionmcp/reference.import.md
What reference.import does on Visionmcp
AI agents use reference.import 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 reference.import is rated Medium
The tool ingests (imports) reference data with metadata, which is a write/create operation. 'Immutable' refers to the nature of the reference data once stored, not an inability to undo the action itself. There's no indication of code execution, deletion, or financial transactions. Severity is medium as importing reference data could affect downstream model behavior or system state.
From the tool's definition Queue immutable reference ingestion with metadata and quality inspection
Attacks that exploit this kind of access
The rule that runs reference.import 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 reference.import, this is the rule to start with:
reference.import 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 reference.import call is checked against it from then on.
Questions about reference.import
Queue immutable reference ingestion with metadata and quality inspection. 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 reference.import: 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.
reference.import 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 reference.import 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 reference.import. 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.
reference.import 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