test_webhook_connection · Make Com MCP Server MCP

WHAT IT DOES

What test_webhook_connection does on Make Com MCP Server

AI agents invoke test_webhook_connection to trigger actions in Make Com 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.

WHY IT NEEDS A POLICY

Why test_webhook_connection needs a policy

Testing a webhook connection involves sending an actual HTTP request to an external endpoint, which may trigger downstream automation scenarios. Even a 'test' call executes an external operation with potential side effects. Severity is medium because test endpoints may fire real workflows depending on Make.com scenario configuration.

From the tool's definition 测试与Make.com webhook的连接 (Test connection with Make.com webhook) — triggers an external webhook call to Make.com

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

test_webhook_connection Rate-limited

test_webhook_connection stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "test_webhook_connection": {
      "limits": [
        {
          "counter": "test_webhook_connection_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Make Com MCP Server, so you can run agents against it safely.

FAQ

Questions about test_webhook_connection

What does the test_webhook_connection tool do? +

测试与Make.com webhook的连接. It is categorised as a Execute tool in the Make Com MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on test_webhook_connection? +

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

What risk level is test_webhook_connection? +

test_webhook_connection is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit test_webhook_connection? +

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

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

test_webhook_connection is provided by the Make Com MCP Server MCP server (joseph19820124/make-mcp-integration-playbook). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.