get_personal_records
AI agents call get_personal_records to retrieve information from Claude Garmin without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The 'get_' prefix and pattern of sibling tools all being read-only data retrievals (get_activities, get_fitness, get_goals, etc.) strongly indicate this tool queries existing user data without modification, deletion, or external side effects. It fits the Read category as a data retrieval operation with minimal blast radius.
From the tool's definition Tool name 'get_personal_records' indicates a retrieval operation. Description is empty, but the sibling tools (all prefixed 'get_') and server context (Garmin Connect data analysis for training metrics) confirm this is a query/fetch operation that retrieves…
Attacks that exploit this kind of access
get_personal_records. It is categorised as a Read tool in the Claude Garmin MCP Server, which means it retrieves data without modifying state.
Register the Claude Garmin MCP server in PolicyLayer and add a rule for get_personal_records: 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 Claude Garmin. Nothing to install.
get_personal_records 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_records 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_records. 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_records is provided by the Claude Garmin MCP server (jack-abyss/claude-garmin). 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 →