AI agents call get_personal_info 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 personal information from an Oura Ring health profile through an OAuth2-authenticated API. It is a read operation that queries data without modification, creation, deletion, or execution of code.
From the tool's definition Tool name is 'get_personal_info' with description 'Get user'. The verb 'get' and action of retrieving user information indicates data retrieval with no side effects.
Documented attack patterns abuse exactly the kind of access get_personal_info 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_personal_info:
{
"version": "1",
"default": "deny",
"tools": {
"get_personal_info": {}
}
}get_personal_info 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 user. 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_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 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 MCP Server MCP server (meimakes/oura-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Oura MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
9 Oura MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.