This record as markdown: /tools/io-github-alxpark-propresenter-mcp/props-clear.md
What props_clear does on Propresenter
AI agents call props_clear to permanently remove resources in Propresenter, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why props_clear is rated Critical
This tool removes data (a prop) from active display in a presentation context. While potentially recoverable from saved files, the action itself on the active presentation state is destructive—it eliminates the prop's visibility and state without reversal through the tool's own mechanism.
From the tool's definition Tool name is 'props_clear' and description states 'Clear a specific prop from display'. The verb 'clear' in the context of presentation software means to remove or delete a prop from the current display, which is an irreversible action that cannot be undone…
Attacks that exploit this kind of access
The rule that runs props_clear 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_clear, this is the rule to start with:
props_clear is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Propresenter, apply this rule, and every props_clear call is checked against it from then on.
Questions about props_clear
Clear a specific prop from display. It is categorised as a Destructive tool in the Propresenter MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Propresenter MCP server in PolicyLayer and add a rule for props_clear: 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_clear is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the props_clear 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_clear. 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_clear 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.
Across the catalogue