AI agents call get_media_by_filename to retrieve information from Wati without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves existing media metadata by filename, with no side effects. It does not create, modify, delete, or execute operations. The blast radius of misuse is minimal—an attacker gains read access to media details already stored in the WATI system, which is a standard data query risk.
From the tool's definition Tool name contains 'get_' and description states 'Retrieve media details' with no modification or destructive operations mentioned. Sibling tools like 'get_contacts_list', 'get_messages', and 'get_message_templates' confirm this is a query/retrieval operation.
Attacks that exploit this kind of access
Retrieve media details from the WATI API by file name. It is categorised as a Read tool in the Wati MCP Server, which means it retrieves data without modifying state.
Register the Wati MCP server in PolicyLayer and add a rule for get_media_by_filename: 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 Wati. Nothing to install.
get_media_by_filename is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_media_by_filename 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 get_media_by_filename. 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.
get_media_by_filename is provided by the Wati MCP server (jairajmehra/wati_whatsapp_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 →