record_notification · Claude Sync MCP: Risk & Policy

WHAT IT DOES

What record_notification does on Claude Sync

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

WHY IT NEEDS A POLICY

Why record_notification needs a policy

This tool writes/records a notification entry into a SQLite database. It creates a new record but does not delete or overwrite existing data, execute arbitrary code, or involve financial transactions. The operation appears to be a simple persistence step following a calendar event creation, making it a reversible write action with low blast radius.

From the tool's definition Record a notification in the DB (after Calendar event was successfully created).

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

record_notification Rate-limited

record_notification 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": {
    "record_notification": {
      "limits": [
        {
          "counter": "record_notification_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 Claude Sync, so you can run agents against it safely.

FAQ

Questions about record_notification

What does the record_notification tool do? +

Record a notification in the DB (after Calendar event was successfully created). It is categorised as a Write tool in the Claude Sync MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on record_notification? +

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

What risk level is record_notification? +

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

Can I rate-limit record_notification? +

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

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

record_notification is provided by the Claude Sync MCP server (the-firmament/claude-sync). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.