Low Risk

stage_get_screens

Get all stage screens and their configurations

How to control stage_get_screens ↓

What stage_get_screens does on Propresenter

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

Low Risk

Why stage_get_screens needs a policy

This tool queries and returns stage screen configurations from ProPresenter 7. It has no side effects, does not execute operations, and does not modify or delete any data. It is a straightforward read operation that retrieves existing information about stage screen configurations.

From the tool's definition Tool name contains 'get' and description states 'Get all stage screens and their configurations' — purely retrieves data without modification, deletion, or execution of operations.

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

How to control stage_get_screens

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

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "stage_get_screens": {}
  }
}

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

  1. Create a free account and register Propresenter — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about stage_get_screens

What does the stage_get_screens tool do? +

Get all stage screens and their configurations. It is categorised as a Read tool in the Propresenter MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on stage_get_screens? +

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

What risk level is stage_get_screens? +

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

Can I rate-limit stage_get_screens? +

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

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

stage_get_screens is provided by the Propresenter MCP server (@alxpark/propresenter-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Propresenter tool call.

Start from Propresenter, 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.

177 Propresenter tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.