AI agents call get_status to retrieve information from Computer Use without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries the state of a virtual computer system and returns that information. There are no side effects, no code execution, no data modification, and no destructive operations. It is purely informational, making it a Read operation with low severity since status queries pose minimal risk even if misused.
From the tool's definition Tool name 'get_status' and description 'Get the current status of the virtual computer' indicate this retrieves status information without modifying, executing operations, or causing side effects.
Documented attack patterns abuse exactly the kind of access get_status gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Computer Use, and nothing reaches the server without passing your rules. This is the rule we recommend for get_status:
{
"version": "1",
"default": "deny",
"tools": {
"get_status": {}
}
}get_status 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.
Get the current status of the virtual computer. It is categorised as a Read tool in the Computer Use MCP Server, which means it retrieves data without modifying state.
Register the Computer Use MCP server in PolicyLayer and add a rule for get_status: 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 Computer Use. Nothing to install.
get_status 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 get_status 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 get_status. 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.
get_status is provided by the Computer Use MCP server (spencerkinney/computer-use-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Computer Use, 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.
15 Computer Use tools catalogued and risk-classified — across an index of 43,000+ MCP servers.