Returns the authenticated user profile: display name, dates, unit system, timezone, and averages. Cached for 1 hour.
AI agents call get_profile to retrieve information from Fitbit Googlehealth without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a straightforward read operation that queries user profile information without side effects. The cached 1-hour response time confirms it is non-destructive. No financial, execution, write, or destructive operations are possible with this tool.
From the tool's definition Tool name 'get_profile' and description 'Returns the authenticated user profile' indicates data retrieval with no modification, deletion, or execution capability.
Attacks that exploit this kind of access
Returns the authenticated user profile: display name, dates, unit system, timezone, and averages. Cached for 1 hour. It is categorised as a Read tool in the Fitbit Googlehealth MCP Server, which means it retrieves data without modifying state.
Register the Fitbit Googlehealth MCP server in PolicyLayer and add a rule for get_profile: 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 Fitbit Googlehealth. Nothing to install.
get_profile 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_profile 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_profile. 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_profile is provided by the Fitbit Googlehealth MCP server (tachibanayu24/fitbit-googlehealth-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 →