zeph_dismiss · Zeph To MCP: Risk & Policy

WHAT IT DOES

What zeph_dismiss does on Zeph To

AI agents use zeph_dismiss 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_dismiss needs a policy

This tool marks a notification as read/dismissed, which is a reversible state change (the notification data still exists, just marked as read). It modifies the state of a notification record but does not permanently delete it. This fits Write rather than Destructive since dismissing a notification is a soft state change, not an irreversible deletion.

From the tool's definition Dismiss (mark as read) a specific push notification by ID. Use after processing a notification to clear it from the user

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

zeph_dismiss Rate-limited

zeph_dismiss 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_dismiss": {
      "limits": [
        {
          "counter": "zeph_dismiss_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_dismiss

What does the zeph_dismiss tool do? +

Dismiss (mark as read) a specific push notification by ID. Use after processing a notification to clear it from 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_dismiss? +

Register the Zeph To MCP server in PolicyLayer and add a rule for zeph_dismiss: 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_dismiss? +

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

Can I rate-limit zeph_dismiss? +

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

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

zeph_dismiss 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.