set_notification_preferences · Run402 MCP: Risk & Policy

WHAT IT DOES

What set_notification_preferences does on Run402

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

WHY IT NEEDS A POLICY

Why set_notification_preferences needs a policy

This tool creates or modifies data (notification preferences, webhook URLs) in a reversible manner. While it touches sensitive configuration, it does not execute arbitrary code, delete data, move money, or perform irreversible actions. The conditional assurance requirements (email_verified, operator_passkey) suggest the system recognizes the sensitivity.

From the tool's definition Tool description explicitly states 'Update operator notification preferences' and mentions changes to 'webhook URL' and conditional email/passkey requirements, indicating modification of user settings and notification configuration.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

set_notification_preferences Rate-limited

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

FAQ

Questions about set_notification_preferences

What does the set_notification_preferences tool do? +

Update operator notification preferences. Cross-wallet effects require email_verified assurance; webhook URL changes require operator_passkey assurance. It is categorised as a Write tool in the Run402 MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on set_notification_preferences? +

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

What risk level is set_notification_preferences? +

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

Can I rate-limit set_notification_preferences? +

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

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

set_notification_preferences is provided by the Run402 MCP server (kychee-com/run402). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.