zeph_dismiss_all · Zeph To MCP: Risk & Policy

WHAT IT DOES

What zeph_dismiss_all does on Zeph To

AI agents use zeph_dismiss_all 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_all needs a policy

This tool modifies data by clearing notifications from a notification feed. While it removes data from the user's view, the underlying notification records likely persist in system logs or can be re-triggered, making it reversible rather than destructively permanent. This qualifies as Write rather than Destructive.

From the tool's definition Tool description states 'Dismiss all push notifications at once. Clears the entire notification feed.' The action modifies state by clearing notifications, which is reversible (notifications can be regenerated or re-sent).

Risk signalsBulk/mass operation — affects multiple targets

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

zeph_dismiss_all Rate-limited

zeph_dismiss_all 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_all": {
      "limits": [
        {
          "counter": "zeph_dismiss_all_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_all

What does the zeph_dismiss_all tool do? +

Dismiss all push notifications at once. Clears the entire notification feed. 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_all? +

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

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

Can I rate-limit zeph_dismiss_all? +

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

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

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