zeph_input · Zeph To MCP: Risk & Policy

WHAT IT DOES

What zeph_input does on Zeph To

AI agents use zeph_input 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_input needs a policy

An AI agent can call zeph_input faster than any human can review — one bad instruction and it creates or modifies resources in Zeph To by the hundred, each call as confident as the last.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

zeph_input Rate-limited

zeph_input 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_input": {
      "limits": [
        {
          "counter": "zeph_input_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_input

What does the zeph_input tool do? +

Request text input from the user via push notification. The tool blocks until the user responds or the timeout is reached. Requires ZEPH_HOOK_ID environment variable. 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_input? +

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

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

Can I rate-limit zeph_input? +

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

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

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