AI agents use props_set_collection 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.
The tool updates (modifies) a specific prop collection in ProPresenter 7. This is a write operation that modifies existing data. It appears reversible (collections can be updated again), so Write is appropriate rather than Destructive. Medium severity because misuse could alter presentation props/overlays used in live productions.
From the tool's definition "Update a specific prop collection"
Documented attack patterns abuse exactly the kind of access props_set_collection 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 props_set_collection:
{
"version": "1",
"default": "deny",
"tools": {
"props_set_collection": {
"limits": [
{
"counter": "props_set_collection_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}props_set_collection 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 a specific prop collection. 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 props_set_collection: 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_set_collection 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 props_set_collection 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_set_collection. 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_set_collection 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.