Take a screenshot of the VM display and return it as an image.
AI agents call screenshot to retrieve information from Vphone without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Screenshots are informational queries that capture current display state. They have no destructive, financial, or state-modifying impact. While the tool could be used for reconnaissance in a test environment, the blast radius is minimal—it only exposes what is visually present on screen at the time of capture. Low severity is appropriate for a read-only diagnostic action.
From the tool's definition Tool description states 'Take a screenshot of the VM display and return it as an image' — a pure read operation that retrieves visual display data without modifying any state or triggering side effects. No arguments that could alter system behavior.
Documented attack patterns abuse exactly the kind of access screenshot gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Vphone, and nothing reaches the server without passing your rules. This is the rule we recommend for screenshot:
{
"version": "1",
"default": "deny",
"tools": {
"screenshot": {}
}
}screenshot is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Take a screenshot of the VM display and return it as an image. It is categorised as a Read tool in the Vphone MCP Server, which means it retrieves data without modifying state.
Register the Vphone MCP server in PolicyLayer and add a rule for screenshot: 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 Vphone. Nothing to install.
screenshot 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 screenshot 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 screenshot. 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.
screenshot is provided by the Vphone MCP server (pluginslab/vphone-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Vphone, 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.
17 Vphone tools catalogued and risk-classified — across an index of 43,000+ MCP servers.