Get activity data for a date range
AI agents call get_activity_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 health/activity data from the Oura Ring API without modifying any state. The verb 'Get' and the read-only nature of summarizing historical activity data clearly places it in the Read category. The data is personal health information but the tool itself cannot cause damage if misused — worst case is unauthorized access to user's activity metrics.
From the tool's definition Tool name is 'get_activity_summary' and description states 'Get activity data for a date range' — both indicate a retrieval operation with no modification or side effects.
Attacks that exploit this kind of access
Get activity 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_activity_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_activity_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_activity_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_activity_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_activity_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 →