AI agents use playlists_set to create or update resources in Propresenter — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Propresenter environment.
This tool creates or modifies playlist data in ProPresenter 7. The operation is reversible—playlists can be re-edited or restored—making it a Write action rather than Destructive. The severity is medium because misuse could disrupt presentation workflows by modifying active playlists, but the effect is not destructive and can be corrected.
From the tool's definition Tool name 'playlists_set' and description 'Update the contents of a specific playlist' indicate modification of data that is reversible.
Documented attack patterns abuse exactly the kind of access playlists_set gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Propresenter, and nothing reaches the server without passing your rules. This is the rule we recommend for playlists_set:
{
"version": "1",
"default": "deny",
"tools": {
"playlists_set": {
"limits": [
{
"counter": "playlists_set_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}playlists_set stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Update the contents of a specific playlist. It is categorised as a Write tool in the Propresenter MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Propresenter MCP server in PolicyLayer and add a rule for playlists_set: 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.
playlists_set is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the playlists_set 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 playlists_set. 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.
playlists_set 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.
Start from Propresenter, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
177 Propresenter tools catalogued and risk-classified — across an index of 43,000+ MCP servers.