phishfort_test_webhook · Phishfort MCP: Risk & Policy

WHAT IT DOES

What phishfort_test_webhook does on Phishfort

AI agents invoke phishfort_test_webhook to trigger actions in Phishfort. 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 phishfort_test_webhook needs a policy

This tool executes an outbound webhook delivery (an external network operation with side effects). It is not merely reading or writing stored data — it actively triggers a real HTTP request to an external system. The 'after approval' gate reduces risk somewhat, but misuse could spam or probe external endpoints.

From the tool's definition 'Send test webhook delivery after approval' — triggers an external HTTP delivery operation to a configured webhook endpoint

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

phishfort_test_webhook Rate-limited

phishfort_test_webhook 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": {
    "phishfort_test_webhook": {
      "limits": [
        {
          "counter": "phishfort_test_webhook_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 Phishfort, so you can run agents against it safely.

FAQ

Questions about phishfort_test_webhook

What does the phishfort_test_webhook tool do? +

Send test webhook delivery after approval. It is categorised as a Execute tool in the Phishfort MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on phishfort_test_webhook? +

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

What risk level is phishfort_test_webhook? +

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

Can I rate-limit phishfort_test_webhook? +

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

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

phishfort_test_webhook is provided by the Phishfort MCP server (mychaelconnolly/phishfort-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.