phishfort_update_webhook · Phishfort MCP: Risk & Policy

WHAT IT DOES

What phishfort_update_webhook does on Phishfort

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

WHY IT NEEDS A POLICY

Why phishfort_update_webhook needs a policy

This tool modifies an existing webhook subscription configuration. While the approval-gating mentioned in the server description provides some safety, the tool fundamentally performs a Write operation—it changes webhook settings that could alter incident notification behavior or redirect security alerts.

From the tool's definition Tool name includes 'update' and description states 'Update webhook subscription after approval.' Updates modify existing webhook configurations, which are reversible changes.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

phishfort_update_webhook Rate-limited

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

FAQ

Questions about phishfort_update_webhook

What does the phishfort_update_webhook tool do? +

Update webhook subscription after approval. It is categorised as a Write tool in the Phishfort MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on phishfort_update_webhook? +

Register the Phishfort MCP server in PolicyLayer and add a rule for phishfort_update_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_update_webhook? +

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

Can I rate-limit phishfort_update_webhook? +

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

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

phishfort_update_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.