pilotgentic_notification_center_manager

WHAT IT DOES

What pilotgentic_notification_center_manager does on PilotGentic

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

WHY IT NEEDS A POLICY

Why pilotgentic_notification_center_manager needs a policy

This tool modifies system notification preferences and states, which are reversible configuration changes. While it affects notification behavior and could be misused to silence alerts or hide important notifications from the user, it does not delete data irreversibly, execute arbitrary code, or cause financial harm.

From the tool's definition Tool description states 'Manage macOS Notification Center' covering 'DND/Focus status, per-app notification settings, alert styles, badge settings' — these are configuration changes (reversible modifications) rather than destructive deletions.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

pilotgentic_notification_center_manager Rate-limited

pilotgentic_notification_center_manager 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": {
    "pilotgentic_notification_center_manager": {
      "limits": [
        {
          "counter": "pilotgentic_notification_center_manager_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 PilotGentic, so you can run agents against it safely.

FAQ

Questions about pilotgentic_notification_center_manager

What does the pilotgentic_notification_center_manager tool do? +

Manage macOS Notification Center: DND/Focus status, per-app notification settings, alert styles, badge settings, and notification history. It is categorised as a Write tool in the PilotGentic MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on pilotgentic_notification_center_manager? +

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

What risk level is pilotgentic_notification_center_manager? +

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

Can I rate-limit pilotgentic_notification_center_manager? +

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

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

pilotgentic_notification_center_manager is provided by the PilotGentic MCP server (@pilotgentic/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.