This record as markdown: /tools/io-github-alxpark-propresenter-mcp/messages-delete.md
What messages_delete does on Propresenter
AI agents call messages_delete 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 messages_delete is rated Critical
Deletion operations are irreversible and cannot be undone without external recovery mechanisms. While the blast radius is scoped to individual messages (not system-wide data), the permanent loss of message content represents a destructive action that merits 'high' severity in a presentation/announcement context where messages may be important operational or archival records.
From the tool's definition Tool name 'messages_delete' with description 'Delete a specific message' - the verb 'Delete' indicates irreversible removal of data.
Attacks that exploit this kind of access
The rule that runs messages_delete 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 messages_delete, this is the rule to start with:
messages_delete 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 messages_delete call is checked against it from then on.
Questions about messages_delete
Delete a specific message. 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 messages_delete: 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.
messages_delete 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 messages_delete 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 messages_delete. 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.
messages_delete 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