Focus the currently active announcement presentation
AI agents invoke announcement_focus_active to trigger actions in Propresenter. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
This tool triggers a UI/presentation action (focusing the active announcement) in ProPresenter 7, which is an external operation affecting the presentation software's state. It doesn't merely read data, but it also doesn't write, delete, or involve finances. Focusing a presentation is a reversible operational action with minimal blast radius.
From the tool's definition Focus the currently active announcement presentation
Documented attack patterns abuse exactly the kind of access announcement_focus_active 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 announcement_focus_active:
{
"version": "1",
"default": "deny",
"tools": {
"announcement_focus_active": {
"limits": [
{
"counter": "announcement_focus_active_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
} announcement_focus_active stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Focus the currently active announcement presentation. It is categorised as a Execute tool in the Propresenter MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Propresenter MCP server in PolicyLayer and add a rule for announcement_focus_active: 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.
announcement_focus_active is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the announcement_focus_active 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 announcement_focus_active. 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.
announcement_focus_active 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.