This record as markdown: /tools/heznpc-airmcp/health-today-steps.md
What health_today_steps does on AirMCP
AI agents call health_today_steps to retrieve information from AirMCP without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why health_today_steps is rated Low
This tool retrieves health metrics (step count) from HealthKit without creating, modifying, deleting, or executing any operations. It is a straightforward read-only query of personal health data. Severity is low because exposure of step count data has minimal immediate blast radius, though it does involve personal health information.
From the tool's definition Tool name 'health_today_steps' and description 'Get aggregated step count for today from HealthKit' indicate data retrieval with no modification or side effects.
Attacks that exploit this kind of access
The rule that runs health_today_steps safely
PolicyLayer is an MCP gateway: it sits between your AI agents and AirMCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For health_today_steps, this is the rule to start with:
health_today_steps 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 AirMCP, apply this rule, and every health_today_steps call is checked against it from then on.
Questions about health_today_steps
Get aggregated step count for today from HealthKit. It is categorised as a Read tool in the AirMCP MCP Server, which means it retrieves data without modifying state.
Register the Air MCP server in PolicyLayer and add a rule for health_today_steps: 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 AirMCP. Nothing to install.
health_today_steps 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_today_steps 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_today_steps. 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_today_steps is provided by the Air MCP server (airmcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Air, and thousands of servers like it.
This server
Across the catalogue