sleep_cycles
Calculate optimal sleep/wake times based on 90-minute sleep cycles.
This record as markdown: /tools/io-tinyfn-tinyfn/sleep-cycles.md
What sleep_cycles does on TinyFn
AI agents call sleep_cycles to retrieve information from TinyFn without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
wake_time | string | — | Desired wake time (HH:MM) |
sleep_time | string | — | Desired sleep time (HH:MM) |
Parameters from the server's own tool schema.
Why sleep_cycles is rated Low
This is a deterministic calculation tool that analyzes sleep cycle data and returns computed recommendations. It performs no write, deletion, execution, or financial operations. The tool fits squarely into the Read category as it retrieves or computes information without causing any irreversible changes or triggering external actions.
From the tool's definition Tool description states it 'Calculate[s] optimal sleep/wake times' — a pure calculation/retrieval operation with no side effects, data modification, code execution, or external state changes.
Attacks that exploit this kind of access
The rule that runs sleep_cycles safely
PolicyLayer is an MCP gateway: it sits between your AI agents and TinyFn, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For sleep_cycles, this is the rule to start with:
sleep_cycles 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 TinyFn, apply this rule, and every sleep_cycles call is checked against it from then on.
Questions about sleep_cycles
Calculate optimal sleep/wake times based on 90-minute sleep cycles. It is categorised as a Read tool in the TinyFn MCP Server, which means it retrieves data without modifying state.
sleep_cycles accepts 2 parameters: wake_time, sleep_time. The full parameter table on this page comes from the server's own tool schema.
Register the TinyFn MCP server in PolicyLayer and add a rule for sleep_cycles: 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 TinyFn. Nothing to install.
sleep_cycles 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 sleep_cycles 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 sleep_cycles. 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.
sleep_cycles is provided by the TinyFn MCP server (https://api.tinyfn.io/mcp/all/). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on TinyFn, and thousands of servers like it.
This server
Across the catalogue