phishfort_report_incident · Phishfort MCP: Risk & Policy

WHAT IT DOES

What phishfort_report_incident does on Phishfort

AI agents use phishfort_report_incident 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_report_incident needs a policy

This tool submits a new incident report to PhishFort, initiating takedown or monitoring actions against a target. It is a Write operation (creating a new incident record) but with high severity because misuse could incorrectly flag legitimate domains for takedown. The 'after approval' qualifier slightly reduces blast radius but the downstream effects (takedown requests) are significant.

From the tool's definition 'Report incident for takedown or monitoring after approval' — creates a new incident report that triggers takedown or monitoring workflows

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

phishfort_report_incident Rate-limited

phishfort_report_incident 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_report_incident": {
      "limits": [
        {
          "counter": "phishfort_report_incident_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_report_incident

What does the phishfort_report_incident tool do? +

Report incident for takedown or monitoring 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_report_incident? +

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

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

Can I rate-limit phishfort_report_incident? +

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

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

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