This record as markdown: /tools/io-github-alxpark-propresenter-mcp/status-get-layers.md
What status_get_layers does on Propresenter
AI agents call status_get_layers 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.
Why status_get_layers is rated Low
This tool queries and returns the state of layers in ProPresenter 7 without modifying data, executing commands, or triggering side effects. It is a straightforward read operation that retrieves information for display or monitoring purposes.
From the tool's definition Tool name 'status_get_layers' and description 'Get the status of all layers' indicate a retrieval operation with no modification or execution of external effects.
Attacks that exploit this kind of access
The rule that runs status_get_layers 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_layers, this is the rule to start with:
status_get_layers 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 Propresenter, apply this rule, and every status_get_layers call is checked against it from then on.
Questions about status_get_layers
Get the status of all layers. It is categorised as a Read tool in the Propresenter MCP Server, which means it retrieves data without modifying state.
Register the Propresenter MCP server in PolicyLayer and add a rule for status_get_layers: 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.
status_get_layers 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 status_get_layers 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 status_get_layers. 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.
status_get_layers 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.
More on Propresenter, and thousands of servers like it.
This server
Across the catalogue