vision.discover_states
Discover only actually observed state, interaction, responsive, and motion evidence.
This record as markdown: /tools/visionmcp/vision.discover-states.md
What vision.discover_states does on Visionmcp
AI agents call vision.discover_states 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.
Why vision.discover_states is rated Low
This tool retrieves or queries observational data (states, interactions, responsiveness, motion) from visual evidence without creating, modifying, executing commands, or deleting anything. It is a discovery/inspection operation with no side effects, characteristic of the Read category.
From the tool's definition Tool name 'discover_states' and description 'Discover only actually observed state, interaction, responsive, and motion evidence' indicate data retrieval and inspection without modification or execution.
Attacks that exploit this kind of access
The rule that runs vision.discover_states 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.discover_states, this is the rule to start with:
vision.discover_states is read-only, so it stays allowed. 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.discover_states call is checked against it from then on.
Questions about vision.discover_states
Discover only actually observed state, interaction, responsive, and motion evidence. It is categorised as a Read tool in the Visionmcp MCP Server, which means it retrieves data without modifying state.
Register the Vision MCP server in PolicyLayer and add a rule for vision.discover_states: 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.discover_states is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the vision.discover_states 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.discover_states. 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.discover_states 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