AI agents call vicsee_list_models to retrieve information from Vicsee without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a read-only tool that retrieves and filters metadata about available models. It performs no creation, modification, deletion, or execution of external operations—only information retrieval. The low severity reflects that misuse (e.g., querying the model list repeatedly) poses minimal harm and no blast radius beyond API quota consumption.
From the tool's definition Tool 'lists available VicSee models' and is described as retrieving model capabilities and credit costs; the description explicitly states 'Call this first to find a model id', indicating a lookup/query operation with no side effects.
Attacks that exploit this kind of access
List available VicSee models with their capabilities and credit costs. Call this first to find a model id to pass to vicsee_generate. Optionally filter by media type. It is categorised as a Read tool in the Vicsee MCP Server, which means it retrieves data without modifying state.
Register the Vicsee MCP server in PolicyLayer and add a rule for vicsee_list_models: 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 Vicsee. Nothing to install.
vicsee_list_models 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 vicsee_list_models 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 vicsee_list_models. 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.
vicsee_list_models is provided by the Vicsee MCP server (vicseeai/vicsee-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →