sendChatTypingIndicator · Xdevplatform/x MCP: Risk & Policy

WHAT IT DOES

What sendChatTypingIndicator does on Xdevplatform/xmcp

AI agents invoke sendChatTypingIndicator to trigger actions in Xdevplatform/xmcp. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.

WHY IT NEEDS A POLICY

Why sendChatTypingIndicator needs a policy

Sending a typing indicator is an external side-effect operation that signals to other users that someone is typing. It doesn't read, write persistent data, or delete anything, but it does trigger an external real-time event on the platform. It's Execute because it initiates an external operation. Severity is low since the blast radius is minimal — it's a transient, ephemeral signal with no lasting impact.

From the tool's definition 'Send a typing indicator in a chat conversation' — triggers an external operation (sends a real-time signal to a chat service)

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

sendChatTypingIndicator Rate-limited

sendChatTypingIndicator stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "sendChatTypingIndicator": {
      "limits": [
        {
          "counter": "sendchattypingindicator_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Xdevplatform/xmcp, so you can run agents against it safely.

FAQ

Questions about sendChatTypingIndicator

What does the sendChatTypingIndicator tool do? +

Send a typing indicator in a chat conversation. It is categorised as a Execute tool in the Xdevplatform/xmcp MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on sendChatTypingIndicator? +

Register the Xdevplatform/x MCP server in PolicyLayer and add a rule for sendChatTypingIndicator: 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 Xdevplatform/xmcp. Nothing to install.

What risk level is sendChatTypingIndicator? +

sendChatTypingIndicator is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit sendChatTypingIndicator? +

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

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

sendChatTypingIndicator is provided by the Xdevplatform/x MCP server (xdevplatform/xmcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.