evidence.register_search_provider
Register a bounded search API after named terms, privacy, and secret review.
This record as markdown: /tools/visionmcp/evidence.register-search-provider.md
What evidence.register_search_provider does on Visionmcp
AI agents use evidence.register_search_provider 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.register_search_provider is rated Medium
The tool registers (creates/writes) a new search provider configuration. 'Register' implies a persistent write operation adding a new entry to the system. It is not purely read-only, nor does it execute arbitrary code or delete data. The mention of 'secret review' suggests it may handle credentials, raising the severity slightly, but the core action is a reversible configuration write.
From the tool's definition Register a bounded search API after named terms, privacy, and secret review.
Attacks that exploit this kind of access
The rule that runs evidence.register_search_provider 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.register_search_provider, this is the rule to start with:
evidence.register_search_provider 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.register_search_provider call is checked against it from then on.
Questions about evidence.register_search_provider
Register a bounded search API after named terms, privacy, and secret review. 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.register_search_provider: 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.register_search_provider 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.register_search_provider 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.register_search_provider. 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.register_search_provider 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