Show a typing indicator in a chat (visible to the other person).
AI agents invoke start_typing to trigger actions in Bluebubbles. 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.
This tool executes an operation that modifies the state of a chat interface (displaying a typing indicator) visible to other participants. It is not merely reading data (Read), nor is it creating/modifying message content (Write), nor is it destructive or financial. It is an Execute category tool because it triggers an external action whose behavioral effects depend on the argument (which chat).
From the tool's definition Tool performs an action 'show a typing indicator in a chat (visible to the other person)' which triggers an external operation with effects that depend on which chat is targeted.
Attacks that exploit this kind of access
Show a typing indicator in a chat (visible to the other person). It is categorised as a Execute tool in the Bluebubbles MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Bluebubbles MCP server in PolicyLayer and add a rule for start_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 Bluebubbles. Nothing to install.
start_typing is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the start_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.
Set action: deny in the PolicyLayer policy for start_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.
start_typing is provided by the Bluebubbles MCP server (metaember/bluebubbles-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →