fork_parity_setup_notifications

WHAT IT DOES

What fork_parity_setup_notifications does on Fork Parity MCP

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

WHY IT NEEDS A POLICY

Why fork_parity_setup_notifications needs a policy

This tool creates or modifies notification channel configurations, which is a reversible write operation. It does not retrieve data (Read), execute arbitrary code (Execute), delete data (Destructive), or move money (Financial). The blast radius is low since misconfiguration of notifications affects only alerting behavior and can be easily corrected.

From the tool's definition Tool name 'fork_parity_setup_notifications' and description 'Configure notification channels for fork parity alerts' indicate creation or modification of notification configuration settings.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

fork_parity_setup_notifications Rate-limited

fork_parity_setup_notifications 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": {
    "fork_parity_setup_notifications": {
      "limits": [
        {
          "counter": "fork_parity_setup_notifications_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 Fork Parity MCP, so you can run agents against it safely.

FAQ

Questions about fork_parity_setup_notifications

What does the fork_parity_setup_notifications tool do? +

Configure notification channels for fork parity alerts. It is categorised as a Write tool in the Fork Parity MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on fork_parity_setup_notifications? +

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

What risk level is fork_parity_setup_notifications? +

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

Can I rate-limit fork_parity_setup_notifications? +

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

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

fork_parity_setup_notifications is provided by the Fork Parity MCP server (moikas-code/fork-parity-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.