This record as markdown: /tools/io-github-heznpc-iconnect/health-summary.md
What health_summary does on Iconnect
AI agents call health_summary 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_summary is rated Low
This tool retrieves aggregated health information for display purposes. It queries existing health data without creating, modifying, deleting, or executing external operations. The read-only nature and lack of side effects classify it as Read category with low severity, as unauthorized access to personal health data poses privacy concerns but the tool itself cannot cause irreversible harm or financial impact.
From the tool's definition Tool name 'health_summary' and description 'Get a combined health dashboard' indicate data retrieval with no modification or side effects. The verb 'Get' and 'dashboard' explicitly denote read-only querying of health data.
Attacks that exploit this kind of access
The rule that runs health_summary 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_summary, this is the rule to start with:
health_summary 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_summary call is checked against it from then on.
Questions about health_summary
Get a combined health dashboard: today. 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_summary: 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_summary 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_summary 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_summary. 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_summary 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