AI agents invoke chat_with_vision to trigger actions in OpenRouter MCP Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
Based on the server context describing 'vision support' and the sibling tool 'list_vision_models', this tool likely submits image/vision data to an AI model and retrieves a response, which constitutes executing an external API call. Empty description lowers confidence significantly.
From the tool's definition Tool name 'chat_with_vision' on a server that provides access to 200+ AI models with vision support; description is empty and uninformative.
Documented attack patterns abuse exactly the kind of access chat_with_vision gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and OpenRouter MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for chat_with_vision:
{
"version": "1",
"default": "deny",
"tools": {
"chat_with_vision": {
"limits": [
{
"counter": "chat_with_vision_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}chat_with_vision stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
chat_with_vision. It is categorised as a Execute tool in the OpenRouter MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the OpenRouter MCP Server MCP server in PolicyLayer and add a rule for chat_with_vision: 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 OpenRouter MCP Server. Nothing to install.
chat_with_vision is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the chat_with_vision 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 chat_with_vision. 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.
chat_with_vision is provided by the OpenRouter MCP Server MCP server (physics91/openrouter-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from OpenRouter MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
9 OpenRouter MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.