get_screen_info

THE RISK

Low Risk

Why get_screen_info needs a policy

This tool only queries and returns display configuration metadata. It performs no write, execution, or destructive operations. The information retrieved is non-sensitive system metadata that does not grant access to user data or enable further attacks without combination with other capabilities. Blast radius if misused is minimal since an AI agent learning monitor configuration alone cannot cause harm.

From the tool's definition Tool description states 'Get display/monitor information (resolution, count, positions)' — retrieves read-only system information about attached displays with no modification capability or side effects.

Documented attack patterns abuse exactly the kind of access get_screen_info gives an agent:

POLICY

How to control get_screen_info

PolicyLayer is an MCP gateway — it sits between your AI agents and OODA Computer Control, and nothing reaches the server without passing your rules. This is the rule we recommend for get_screen_info:

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_screen_info": {}
  }
}

get_screen_info is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

Create a free account and register OODA Computer Control — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

CAP THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More OODA Computer Control tools

Destructive batch_delete_files Delete multiple files in parallel. Destructive clear_old_logs Delete audit log entries older than specified days. Use dryRun=true to preview. Destructive clipboard_clear Clear the clipboard. Destructive crud_batch_delete Delete multiple records in parallel. Destructive crud_delete Delete a record Destructive delete_file Delete a file or directory. For multiple deletions, use batch_delete_files. Destructive reset_config Reset configuration to defaults. Optionally specify a section to reset only that section. Destructive kill_process Kill a process by PID or name.

All 99 OODA Computer Control tools →

Read tools on other servers

M-Team MCP Server get_torrent_detail YouTube MCP Server search_channel Android Forensics ADB MCP Server parse_browser_history 0xarchive web3_challenge

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Data exfiltration → How read access becomes an exfiltration channel when chained with untrusted content.
MCP token cost → What connecting this server costs in context-window tokens on every request.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about get_screen_info

What does the get_screen_info tool do? +

Get display/monitor information (resolution, count, positions). It is categorised as a Read tool in the OODA Computer Control MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_screen_info? +

Register the OODA Computer Control MCP server in PolicyLayer and add a rule for get_screen_info: 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 OODA Computer Control. Nothing to install.

What risk level is get_screen_info? +

get_screen_info is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_screen_info? +

Yes. Add a rate_limit block to the get_screen_info 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.

How do I block get_screen_info completely? +

Set action: deny in the PolicyLayer policy for get_screen_info. 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.

What MCP server provides get_screen_info? +

get_screen_info is provided by the OODA Computer Control MCP server (mnehmos/mnehmos.ooda.mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every OODA Computer Control tool call.

Start from OODA Computer Control, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →