status_get_screens

Get the current status of all screens in ProPresenter

SERVERPropresenter SOURCE@alxpark/propresenter-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/io-github-alxpark-propresenter-mcp/status-get-screens.md

WHAT IT DOES

What status_get_screens does on Propresenter

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

RISK

Why status_get_screens is rated Low

This tool queries the current state of screens in ProPresenter and returns status information. It performs no write, execute, destructive, or financial operations. The action is purely informational and read-only, making it the lowest risk category.

From the tool's definition Tool name 'status_get_screens' and description 'Get the current status of all screens in ProPresenter' indicate a retrieval operation with no modification or side effects.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs status_get_screens safely

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

status_get_screens Allowed

status_get_screens 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": {
    "status_get_screens": {}
  }
}

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

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

FAQ

Questions about status_get_screens

What does the status_get_screens tool do? +

Get the current status of all screens in ProPresenter. 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 status_get_screens? +

Register the Propresenter MCP server in PolicyLayer and add a rule for status_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 status_get_screens? +

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

Can I rate-limit status_get_screens? +

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

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

status_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.

KEEP EXPLORING

More on Propresenter, and thousands of servers like it.

This server

All 177 Propresenter tools →

Across the catalogue

get_task_status on 0rca Dojo MCP Server →get_cocktail_by_category on Cocktails RAG MCP Server →get_torrent_detail on M-Team MCP Server →aiva_get_affiliate on AIVA MCP Server → The MCP Attack Database →

Guides

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