sync_health_to_obsidian · Google Health MCP: Risk & Policy

WHAT IT DOES

What sync_health_to_obsidian does on Google Health

AI agents use sync_health_to_obsidian to create or update resources in Google Health — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Google Health environment.

WHY IT NEEDS A POLICY

Why sync_health_to_obsidian needs a policy

This tool creates or writes markdown files to an Obsidian vault directory. It is a Write operation (creating/updating notes) rather than Destructive since it exports/creates files rather than deleting them. Severity is medium because it writes potentially sensitive health data to the filesystem, but the operation is reversible (files can be deleted).

From the tool's definition Export daily health summaries to Obsidian as per-day markdown notes under {vault}/Lifestyle/Health/

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

sync_health_to_obsidian Rate-limited

sync_health_to_obsidian stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "sync_health_to_obsidian": {
      "limits": [
        {
          "counter": "sync_health_to_obsidian_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Google Health, so you can run agents against it safely.

FAQ

Questions about sync_health_to_obsidian

What does the sync_health_to_obsidian tool do? +

Export daily health summaries to Obsidian as per-day markdown notes under {vault}/Lifestyle/Health/. It is categorised as a Write tool in the Google Health MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on sync_health_to_obsidian? +

Register the Google Health MCP server in PolicyLayer and add a rule for sync_health_to_obsidian: 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 Google Health. Nothing to install.

What risk level is sync_health_to_obsidian? +

sync_health_to_obsidian is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit sync_health_to_obsidian? +

Yes. Add a rate_limit block to the sync_health_to_obsidian 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 sync_health_to_obsidian completely? +

Set action: deny in the PolicyLayer policy for sync_health_to_obsidian. 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 sync_health_to_obsidian? +

sync_health_to_obsidian is provided by the Google Health MCP server (madfreakz/google-health-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.