phishfort_add_attachments · Phishfort MCP: Risk & Policy

WHAT IT DOES

What phishfort_add_attachments does on Phishfort

AI agents use phishfort_add_attachments 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_add_attachments needs a policy

This tool creates new incident attachments, which is a reversible Write operation. It does not delete or execute arbitrary code, and approval gating further reduces severity below Execute/Destructive. Severity is medium rather than low because malicious attachments (malware, phishing payloads) could harm downstream analysis if approved, and the tool modifies incident records that others rely on.

From the tool's definition Tool description states 'Add attachment files to an existing incident after approval' — this creates/modifies incident data by attaching files. The 'after approval' qualifier indicates controls are in place to mitigate misuse.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

phishfort_add_attachments Rate-limited

phishfort_add_attachments 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_add_attachments": {
      "limits": [
        {
          "counter": "phishfort_add_attachments_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_add_attachments

What does the phishfort_add_attachments tool do? +

Add attachment files to an existing incident 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_add_attachments? +

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

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

Can I rate-limit phishfort_add_attachments? +

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

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

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