Set or disable the Whoop alarm. Time in HH:MM format.
AI agents use set_alarm to create or update resources in Whoop MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Whoop MCP Server environment.
This tool modifies alarm configuration state on the Whoop device/app, which is a reversible write operation. It does not delete data (Destructive), execute arbitrary code (Execute), involve financial transactions (Financial), or trigger irreversible changes. The impact is limited to user-controlled alarm settings with minimal blast radius if misconfigured by an AI agent.
From the tool's definition Tool description states 'Set or disable the Whoop alarm,' which are reversible modifications to alarm settings. The time parameter (HH:MM format) is a configuration input that can be subsequently changed or disabled.
Attacks that exploit this kind of access
Set or disable the Whoop alarm. Time in HH:MM format. It is categorised as a Write tool in the Whoop MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Whoop MCP Server MCP server in PolicyLayer and add a rule for set_alarm: 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 Whoop MCP Server. Nothing to install.
set_alarm 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 set_alarm 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 set_alarm. 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.
set_alarm is provided by the Whoop MCP Server MCP server (jd1207/whoop-mcp). 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 →