zeph_notify · Zeph To MCP: Risk & Policy

WHAT IT DOES

What zeph_notify does on Zeph To

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

WHY IT NEEDS A POLICY

Why zeph_notify needs a policy

This tool creates transient user-facing notifications. While it modifies the user's notification state (Write), it is not destructive (reversible), does not execute arbitrary code or commands (Execute), involves no financial obligation (Financial), and has minimal blast radius. The notification is one-way with no confirmation or input requested, distinguishing it from zeph_prompt or zeph_ask.

From the tool's definition Tool sends a 'one-way push notification' to the user. This creates a new notification record/message as a reversible side effect without triggering external operations or modifying persistent data structures.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

zeph_notify Rate-limited

zeph_notify 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": {
    "zeph_notify": {
      "limits": [
        {
          "counter": "zeph_notify_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 Zeph To, so you can run agents against it safely.

FAQ

Questions about zeph_notify

What does the zeph_notify tool do? +

Send a one-way push notification to the user\. It is categorised as a Write tool in the Zeph To MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on zeph_notify? +

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

What risk level is zeph_notify? +

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

Can I rate-limit zeph_notify? +

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

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

zeph_notify is provided by the Zeph To MCP server (zeph-to/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.