AI agents invoke vitour_open_page to trigger actions in Mcp. 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.
This tool starts a server process and opens a browser session via Playwright, which involves executing external processes and initiating a persistent session. It triggers external operations (server startup, browser launch) whose effects depend on the arguments provided, making it an Execute category action. Severity is medium as it opens a browser session that can be further exploited by follow-up browser_* tools.
From the tool's definition 'Start Vitour static server, open a Playwright session on a Vitour page, and keep the session open for follow-up browser_* tools'
Attacks that exploit this kind of access
Start Vitour static server, open a Playwright session on a Vitour page, and keep the session open for follow-up browser_* tools. It is categorised as a Execute tool in the Mcp MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the MCP server in PolicyLayer and add a rule for vitour_open_page: 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 Mcp. Nothing to install.
vitour_open_page 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 vitour_open_page 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 vitour_open_page. 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.
vitour_open_page is provided by the MCP server (victormyschik/mcp). 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 →