Low Risk

health.list_changes

List health sync commits after an optional cursor, with optional per-date raw type details from raw manifests.

How to control health.list_changes ↓

What health.list_changes does on Nucleus Apple

AI agents call health.list_changes to retrieve information from Nucleus Apple without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

Why health.list_changes needs a policy

This tool retrieves and queries historical health data changes (sync commits) without creating, modifying, or deleting any data. It is purely informational, fitting the 'Read' category. The severity is low because it only exposes health metadata/commit history, not sensitive health records themselves, and has no side effects. Confidence is high due to clear read-only semantics.

From the tool's definition Tool is named 'list_changes' and described as 'List health sync commits after an optional cursor, with optional per-date raw type details from raw manifests.' The verbs 'list' and the retrieval-focused description indicate read-only data access with no…

Documented attack patterns abuse exactly the kind of access health.list_changes gives an agent:

How to control health.list_changes

PolicyLayer is an MCP gateway — it sits between your AI agents and Nucleus Apple, and nothing reaches the server without passing your rules. This is the rule we recommend for health.list_changes:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "health.list_changes": {}
  }
}

health.list_changes is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Nucleus Apple — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about health.list_changes

What does the health.list_changes tool do? +

List health sync commits after an optional cursor, with optional per-date raw type details from raw manifests. It is categorised as a Read tool in the Nucleus Apple MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on health.list_changes? +

Register the Nucleus Apple MCP server in PolicyLayer and add a rule for health.list_changes: 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 Nucleus Apple. Nothing to install.

What risk level is health.list_changes? +

health.list_changes is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit health.list_changes? +

Yes. Add a rate_limit block to the health.list_changes 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.

How do I block health.list_changes completely? +

Set action: deny in the PolicyLayer policy for health.list_changes. 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.

What MCP server provides health.list_changes? +

health.list_changes is provided by the Nucleus Apple MCP server (zish-rob-crur/nucleus-apple-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Nucleus Apple tool call.

Start from Nucleus Apple, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

Free to start. No card required.

30 Nucleus Apple tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.