AI agents call get_today_readiness_data 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 health metrics (readiness data) from the Oura API for the current day. It performs a read-only query operation that does not modify, delete, or execute any actions. No financial impact, no code execution, and no irreversible changes. The blast radius of misuse is minimal—an agent could only query the user's own health data, which is already stored and not modified.
From the tool's definition Tool name is 'get_today_readiness_data' with description 'Get readiness data for today.' The verb 'get' and the server description 'Enables querying sleep, readiness, and resilience data' indicate data retrieval with no side effects.
Documented attack patterns abuse exactly the kind of access get_today_readiness_data gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Oura MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for get_today_readiness_data:
{
"version": "1",
"default": "deny",
"tools": {
"get_today_readiness_data": {}
}
}get_today_readiness_data is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Get readiness data for today. 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_today_readiness_data: 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_today_readiness_data 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_today_readiness_data 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_today_readiness_data. 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_today_readiness_data is provided by the Oura MCP Server MCP server (tomekkorbak/oura-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 6 Oura MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
6 Oura MCP Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.