This record as markdown: /tools/io-github-alxpark-propresenter-mcp/timers-get.md
What timers_get does on Propresenter
AI agents call timers_get to retrieve information from Propresenter without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why timers_get is rated Low
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.
Attacks that exploit this kind of access
The rule that runs timers_get 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 timers_get, this is the rule to start with:
timers_get is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Propresenter, apply this rule, and every timers_get call is checked against it from then on.
Questions about timers_get
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.
More on Propresenter, and thousands of servers like it.
This server
Across the catalogue