This record as markdown: /tools/io-github-alxpark-propresenter-mcp/props-get.md
What props_get does on Propresenter
AI agents call props_get 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 props_get is rated Low
The tool retrieves or queries information about a prop object in ProPresenter 7. The verb 'get' and the absence of any language suggesting side effects (create, modify, delete, execute, trigger) indicate this is a read-only operation. The severity is low because retrieving prop details poses minimal risk—it cannot modify state, execute code, or cause destructive changes.
From the tool's definition Tool name 'props_get' with description 'Get details of a specific prop' indicates a retrieval operation with no modification or execution capability.
Attacks that exploit this kind of access
The rule that runs props_get 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 props_get, this is the rule to start with:
props_get 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 props_get call is checked against it from then on.
Questions about props_get
Get details of a specific prop. 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 props_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 Propresenter. Nothing to install.
props_get 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 props_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.
Set action: deny in the PolicyLayer policy for props_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.
props_get 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