screen_context_resolve
Resolve vague on-screen references like
This record as markdown: /tools/cowork-os/screen-context-resolve.md
What screen_context_resolve does on CoWork OS
AI agents call screen_context_resolve to retrieve information from CoWork OS without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why screen_context_resolve is rated Low
The tool appears to read/analyze screen content to resolve contextual references. This is a read operation (capturing screen state), but carries medium severity because screen capture can expose sensitive information visible on screen. Description is incomplete, which lowers confidence slightly.
From the tool's definition 'Resolve vague on-screen references' — the tool reads and interprets what is currently displayed on screen
Attacks that exploit this kind of access
The rule that runs screen_context_resolve safely
PolicyLayer is an MCP gateway: it sits between your AI agents and CoWork OS, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For screen_context_resolve, this is the rule to start with:
screen_context_resolve is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect CoWork OS, apply this rule, and every screen_context_resolve call is checked against it from then on.
Questions about screen_context_resolve
Resolve vague on-screen references like. It is categorised as a Read tool in the CoWork OS MCP Server, which means it retrieves data without modifying state.
Register the CoWork OS MCP server in PolicyLayer and add a rule for screen_context_resolve: 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 CoWork OS. Nothing to install.
screen_context_resolve 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 screen_context_resolve 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 screen_context_resolve. 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.
screen_context_resolve is provided by the CoWork OS MCP server (CoWork-OS/CoWork-OS). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on CoWork OS, and thousands of servers like it.
This server
Across the catalogue