health_sleep
Get total sleep hours for a given date (defaults to last night). Only counts actual sleep stages, not time in bed.
This record as markdown: /tools/io-github-heznpc-iconnect/health-sleep.md
What health_sleep does on Iconnect
AI agents call health_sleep to retrieve information from Iconnect without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why health_sleep is rated Low
This tool retrieves health metrics (sleep data) without creating, modifying, deleting, or executing any operations. It is a straightforward read operation accessing the user's stored health information. Severity is low because exposure of this tool poses minimal risk; an AI agent misuse would only result in reading personal sleep data, not altering system state or triggering external actions.
From the tool's definition Tool description states 'Get total sleep hours for a given date' — a retrieval operation with no modification or execution capability. The qualifier 'Only counts actual sleep stages, not time in bed' confirms it is a passive query of existing health data.
Attacks that exploit this kind of access
The rule that runs health_sleep safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Iconnect, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For health_sleep, this is the rule to start with:
health_sleep 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 Iconnect, apply this rule, and every health_sleep call is checked against it from then on.
Questions about health_sleep
Get total sleep hours for a given date (defaults to last night). Only counts actual sleep stages, not time in bed. It is categorised as a Read tool in the Iconnect MCP Server, which means it retrieves data without modifying state.
Register the Iconnect MCP server in PolicyLayer and add a rule for health_sleep: 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 Iconnect. Nothing to install.
health_sleep 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 health_sleep 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 health_sleep. 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.
health_sleep is provided by the Iconnect MCP server (iconnect-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Iconnect, and thousands of servers like it.
This server
Across the catalogue