stop_typing

THE RISK

Low Risk

Why stop_typing needs a policy

Based on the name alone, this tool likely sends a 'stopped typing' indicator to a chat channel — a transient UI signal with no persistent data changes, no code execution, and no financial impact. This is a minor status notification. Confidence is low due to empty description.

From the tool's definition Tool name is 'stop_typing'; description is empty and uninformative.

Documented attack patterns abuse exactly the kind of access stop_typing gives an agent:

POLICY

How to control stop_typing

PolicyLayer is an MCP gateway — it sits between your AI agents and Zulip, and nothing reaches the server without passing your rules. This is the rule we recommend for stop_typing:

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "stop_typing": {
      "limits": [
        {
          "counter": "stop_typing_rate",
          "window": "minute",
          "max": 60,
          "scope": "grant"
        }
      ]
    }
  }
}

stop_typing gets a rate cap, and everything else on the server is denied unless you say otherwise.

Create a free account and register Zulip — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

SET A RULE FOR THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Zulip tools

Destructive remove_reaction Remove an emoji reaction from a message. Write reply Reply in the current session context. Write add_reaction Add an emoji reaction to a message. Write edit_message edit_message Write move_messages move_messages Write resolve_topic resolve_topic Write send_direct_message Send a direct message (DM) to one or more users. Write send_message Send a message to a specific stream and topic (fire-and-forget).

All 27 Zulip tools →

Other tools on other servers

Android Forensics ADB MCP Server generate_app_analysis_report Ethereum Tools add Math MCP Server complex_analysis_suite Crypto_MCP aes_encrypt

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Tool risk categories → How PolicyLayer classifies MCP tools by what they can do.
MCP tool → What an MCP tool is and how clients discover and call it.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about stop_typing

What does the stop_typing tool do? +

stop_typing. It is categorised as a Other tool in the Zulip MCP Server, which means it performs auxiliary operations.

How do I enforce a policy on stop_typing? +

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

What risk level is stop_typing? +

stop_typing is a Other tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit stop_typing? +

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

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

stop_typing is provided by the Zulip MCP server (windborne/zulipmcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Zulip tool call.

Start from Zulip, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →