AI agents use whatsapp_import_folder to create or update resources in Vcon — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Vcon environment.
An AI agent can call whatsapp_import_folder faster than any human can review — one bad instruction and it creates or modifies resources in Vcon by the hundred, each call as confident as the last.
Attacks that exploit this kind of access
Import all WhatsApp .txt files from a folder. Defaults to sample-data directory. It is categorised as a Write tool in the Vcon MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Vcon MCP server in PolicyLayer and add a rule for whatsapp_import_folder: 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 Vcon. Nothing to install.
whatsapp_import_folder is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the whatsapp_import_folder 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 whatsapp_import_folder. 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.
whatsapp_import_folder is provided by the Vcon MCP server (vcon-dev/vcon-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.