Log a Whoop journal entry. Use get_journal_behaviors to find behavior IDs.
AI agents use log_journal 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 writes/creates a new journal entry in the Whoop platform. It is a reversible write operation (entries can typically be deleted), not destructive. The blast radius is medium as it modifies personal health journal data, but does not delete, execute code, or involve finances.
From the tool's definition 'Log a Whoop journal entry' — creates a new journal entry record in the Whoop system
Attacks that exploit this kind of access
Log a Whoop journal entry. Use get_journal_behaviors to find behavior IDs. 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 log_journal: 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.
log_journal 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 log_journal 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 log_journal. 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.
log_journal 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 →