phishfort_rotate_webhook_secret

WHAT IT DOES

What phishfort_rotate_webhook_secret does on Phishfort

AI agents use phishfort_rotate_webhook_secret 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_rotate_webhook_secret needs a policy

Rotating a webhook secret modifies the credential used to authenticate webhook deliveries. This is a Write action (it changes/regenerates a secret), but it carries high severity because it invalidates the previous secret, potentially breaking existing webhook integrations. It is not Destructive because the webhook itself is not deleted and the action can be remediated by rotating again.

From the tool's definition 'Rotate webhook secret. One-time secret is saved locally, not returned.'

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

phishfort_rotate_webhook_secret Rate-limited

phishfort_rotate_webhook_secret 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_rotate_webhook_secret": {
      "limits": [
        {
          "counter": "phishfort_rotate_webhook_secret_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_rotate_webhook_secret

What does the phishfort_rotate_webhook_secret tool do? +

Rotate webhook secret. One-time secret is saved locally, not returned. 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_rotate_webhook_secret? +

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

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

Can I rate-limit phishfort_rotate_webhook_secret? +

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

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

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