send_wecom_file · WeCom Bot MCP Server MCP: Risk & Policy

WHAT IT DOES

What send_wecom_file does on WeCom Bot MCP Server

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

WHY IT NEEDS A POLICY

Why send_wecom_file needs a policy

This tool sends/uploads files through WeCom bots, which is a reversible Write operation. It creates new communication artifacts but does not execute code, delete data, or move money. The tool description is empty, lowering confidence slightly, but the contextual pattern from sibling tools and the naming convention strongly suggest file transmission capability.

From the tool's definition Tool name 'send_wecom_file' combined with server context of sending messages via WeCom bots. Sibling tools include 'send_message', 'send_wecom_image', and 'send_wecom_template_card_*' which are all Write operations.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

send_wecom_file Rate-limited

send_wecom_file 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": {
    "send_wecom_file": {
      "limits": [
        {
          "counter": "send_wecom_file_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 WeCom Bot MCP Server, so you can run agents against it safely.

FAQ

Questions about send_wecom_file

What does the send_wecom_file tool do? +

send_wecom_file. It is categorised as a Write tool in the WeCom Bot 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 send_wecom_file? +

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

What risk level is send_wecom_file? +

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

Can I rate-limit send_wecom_file? +

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

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

send_wecom_file is provided by the WeCom Bot MCP Server MCP server (loonghao/wecom-bot-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.