AI agents call timers_get to retrieve information from Propresenter without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves information about an existing timer without modifying, deleting, or executing any operations. It is a straightforward query operation typical of Read category tools. The low severity reflects minimal risk if misused by an AI agent—exposing timer details poses no security or operational threat.
From the tool's definition Tool name 'timers_get' and description 'Get details of a specific timer' indicate a retrieval operation with no side effects.
Documented attack patterns abuse exactly the kind of access timers_get 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 timers_get:
{
"version": "1",
"default": "deny",
"tools": {
"timers_get": {}
}
}timers_get is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Get details of a specific timer. It is categorised as a Read tool in the Propresenter MCP Server, which means it retrieves data without modifying state.
Register the Propresenter MCP server in PolicyLayer and add a rule for timers_get: 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.
timers_get is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the timers_get 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 timers_get. 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.
timers_get 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.