Get sleep data for a date range
AI agents call get_sleep_summary to retrieve information from Oura MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves historical sleep data for specified date ranges. It performs a query operation with no side effects—no data is created, modified, deleted, or financial transactions are initiated. The data is sensitive personal health information, but the risk is limited to unauthorized access (a Read permission concern), not execution of arbitrary code or destructive/financial operations.
From the tool's definition Tool name 'get_sleep_summary' and description 'Get sleep data for a date range' indicate data retrieval without modification. The server description confirms these are 'access' and 'API calls' to retrieve health data through OAuth2 authentication.
Attacks that exploit this kind of access
Get sleep data for a date range. It is categorised as a Read tool in the Oura MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Oura MCP Server MCP server in PolicyLayer and add a rule for get_sleep_summary: 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 Oura MCP Server. Nothing to install.
get_sleep_summary 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_sleep_summary 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_sleep_summary. 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_sleep_summary is provided by the Oura MCP Server MCP server (slashdevcorpse/oura-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 →