Get user personal information including age, weight, height, biological sex, and timezone
AI agents call get_personal_info to retrieve information from Oura Ring 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 personal metadata about the user from the Oura Ring API. It performs a read-only query with no capability to modify data, execute code, delete information, or initiate financial transactions. The data returned (age, weight, height, biological sex, timezone) is user profile information.
From the tool's definition Tool name 'get_personal_info' and description 'Get user personal information including age, weight, height, biological sex, and timezone' indicate data retrieval with no modification or side effects.
Attacks that exploit this kind of access
Get user personal information including age, weight, height, biological sex, and timezone. It is categorised as a Read tool in the Oura Ring MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Oura Ring MCP Server MCP server in PolicyLayer and add a rule for get_personal_info: 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 Ring MCP Server. Nothing to install.
get_personal_info 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_personal_info 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_personal_info. 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_personal_info is provided by the Oura Ring MCP Server MCP server (jameslouie/oura-ring-mcp). 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 →