whatsapp_post_video_status · WSAPI WhatsApp MCP Server MCP

WHAT IT DOES

What whatsapp_post_video_status does on WSAPI WhatsApp MCP Server

AI agents use whatsapp_post_video_status to create or update resources in WSAPI WhatsApp MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your WSAPI WhatsApp MCP Server environment.

WHY IT NEEDS A POLICY

Why whatsapp_post_video_status needs a policy

This tool creates new data (a video status) on the user's WhatsApp account visible to their contacts. While reversible (users can delete statuses), it modifies account state and publishes content, making it a Write operation rather than Read.

From the tool's definition whatsapp_post_video_status: 'Post a video status update' — creates and publishes new content to WhatsApp status, a permanent public-facing feature until explicitly deleted by the user.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

whatsapp_post_video_status Rate-limited

whatsapp_post_video_status 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": {
    "whatsapp_post_video_status": {
      "limits": [
        {
          "counter": "whatsapp_post_video_status_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 WSAPI WhatsApp MCP Server, so you can run agents against it safely.

FAQ

Questions about whatsapp_post_video_status

What does the whatsapp_post_video_status tool do? +

Post a video status update. Provide either data (base64) or url. It is categorised as a Write tool in the WSAPI WhatsApp MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on whatsapp_post_video_status? +

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

What risk level is whatsapp_post_video_status? +

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

Can I rate-limit whatsapp_post_video_status? +

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

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

whatsapp_post_video_status is provided by the WSAPI WhatsApp MCP Server MCP server (wsapi-chat/wsapi-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.