indicate_typing
AI agents invoke indicate_typing to trigger actions in PyWA MCP Server. 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.
Based on the tool name and server context (WhatsApp Business API), 'indicate_typing' likely triggers a typing indicator in a WhatsApp conversation — an external operation with a visible side effect. This is an Execute-level action as it triggers an external operation, though the blast radius is relatively low since it only shows a transient typing status. Confidence is reduced due to the empty description.
From the tool's definition Tool name 'indicate_typing' on a WhatsApp Business API server; description is empty and uninformative.
Attacks that exploit this kind of access
indicate_typing. It is categorised as a Execute tool in the PyWA MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the PyWA MCP Server MCP server in PolicyLayer and add a rule for indicate_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 PyWA MCP Server. Nothing to install.
indicate_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 indicate_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 indicate_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.
indicate_typing is provided by the PyWA MCP Server MCP server (jem-hr/pywa-mcp-server). 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 →