health_authorize
Request read-only HealthKit authorization. Call this first if other health tools return permission errors.
This record as markdown: /tools/io-github-heznpc-iconnect/health-authorize.md
What health_authorize does on Iconnect
AI agents call health_authorize to retrieve information from Iconnect without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why health_authorize is rated Low
This tool requests read-only authorization to HealthKit data. While it doesn't directly read health data itself, it grants access permissions to sensitive personal health information. Classified as Read because it sets up read-only access. Medium severity because health data is sensitive/personal, but the tool itself only requests authorization rather than exfiltrating data directly.
From the tool's definition Request read-only HealthKit authorization
Attacks that exploit this kind of access
The rule that runs health_authorize safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Iconnect, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For health_authorize, this is the rule to start with:
health_authorize is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Iconnect, apply this rule, and every health_authorize call is checked against it from then on.
Questions about health_authorize
Request read-only HealthKit authorization. Call this first if other health tools return permission errors. It is categorised as a Read tool in the Iconnect MCP Server, which means it retrieves data without modifying state.
Register the Iconnect MCP server in PolicyLayer and add a rule for health_authorize: 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 Iconnect. Nothing to install.
health_authorize 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 health_authorize 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 health_authorize. 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.
health_authorize is provided by the Iconnect MCP server (iconnect-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Iconnect, and thousands of servers like it.
This server
Across the catalogue