main_screen_get

SERVERBreakpoint SOURCEbreakpoint-mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/breakpoint-mcp/main-screen-get.md

WHAT IT DOES

What main_screen_get does on Breakpoint

AI agents call main_screen_get to retrieve information from Breakpoint without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why main_screen_get is rated Low

Even though main_screen_get only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs main_screen_get safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Breakpoint, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For main_screen_get, this is the rule to start with:

main_screen_get Allowed

main_screen_get is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

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

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Breakpoint, apply this rule, and every main_screen_get call is checked against it from then on.

FAQ

Questions about main_screen_get

What does the main_screen_get tool do? +

Report which main-screen editor tab is active (2D / 3D / Script / …) and which are available. Read-only. The active tab decides which viewport screenshot_editor can actually capture: Godot collapses the inactive tab's viewport to a few pixels. It is categorised as a Read tool in the Breakpoint MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on main_screen_get? +

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

What risk level is main_screen_get? +

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

Can I rate-limit main_screen_get? +

Yes. Add a rate_limit block to the main_screen_get 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 main_screen_get completely? +

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

main_screen_get is provided by the Breakpoint MCP server (breakpoint-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Breakpoint, and thousands of servers like it.

This server

All 280 Breakpoint tools →

Across the catalogue

get_cocktail_by_category on Cocktails RAG MCP Server →get_file_snippet on ACE-MCP →get_torrent_detail on M-Team MCP Server →get_customer_data on 08-AI-Business-Agent → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →