model.list
List model approvals/installations and the no-silent-download policy.
This record as markdown: /tools/visionmcp/model.list.md
What model.list does on Visionmcp
AI agents call model.list 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 model.list is rated Low
This tool retrieves and displays existing model approval/installation data and policy settings without creating, modifying, deleting, or executing any operations. It is a straightforward query operation that poses minimal risk if misused by an AI agent, as it only exposes informational content without capability for consequential actions.
From the tool's definition The tool 'model.list' with description 'List model approvals/installations and the no-silent-download policy' performs information retrieval only.
Attacks that exploit this kind of access
The rule that runs model.list 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 model.list, this is the rule to start with:
model.list 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 model.list call is checked against it from then on.
Questions about model.list
List model approvals/installations and the no-silent-download policy. 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 model.list: 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.
model.list 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 model.list 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 model.list. 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.
model.list 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