evidence.acquire
Register provenance and rights, then ingest a permitted local working reference.
This record as markdown: /tools/visionmcp/evidence.acquire.md
What evidence.acquire does on Visionmcp
AI agents use evidence.acquire 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 evidence.acquire is rated Medium
The tool writes/creates new data by registering provenance and rights metadata and ingesting a local file reference into the system. This is a Write operation — it creates records and imports data but does not irreversibly destroy anything, execute code, or involve financial transactions.
From the tool's definition Register provenance and rights, then ingest a permitted local working reference
Attacks that exploit this kind of access
The rule that runs evidence.acquire 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.acquire, this is the rule to start with:
evidence.acquire 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 evidence.acquire call is checked against it from then on.
Questions about evidence.acquire
Register provenance and rights, then ingest a permitted local working reference. 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 evidence.acquire: 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.
evidence.acquire 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 evidence.acquire 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 evidence.acquire. 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.
evidence.acquire 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