get_timer_status
AI agents call get_timer_status to retrieve information from Slack MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool appears to read the status of an active Pomodoro timer. Based on naming convention and sibling tools that manage timers, it retrieves information without creating, modifying, or deleting data. Low severity because timer status queries cannot cause harm even if misused.
From the tool's definition Tool name 'get_timer_status' indicates a query/retrieval operation. Description is empty, but context from sibling tools (cancel_pomodoro_timer, list_active_timers) suggests this retrieves Pomodoro timer state without modification. No side effects expected.
Attacks that exploit this kind of access
get_timer_status. It is categorised as a Read tool in the Slack MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Slack MCP Server MCP server in PolicyLayer and add a rule for get_timer_status: 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 Slack MCP Server. Nothing to install.
get_timer_status 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 get_timer_status 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 get_timer_status. 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.
get_timer_status is provided by the Slack MCP Server MCP server (yeoamlog/slack-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →