AI agents call phishfort_find_incident_by_subject to retrieve information from Phishfort without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves incident data based on search parameters without creating, modifying, deleting, or executing any operations. It is a pure query/lookup function that returns incident information. The approval-gated write architecture mentioned in the server description applies to other tools (add_attachments, add_comment, create_webhook, delete_webhook) but not to this read operation.
From the tool's definition Tool description states 'Find one incident' by specific search criteria (URL, domain, or subject). The verb 'find' and the read-only nature of querying incidents by subject/domain/URL indicate data retrieval with no modification or side effects.
Attacks that exploit this kind of access
Find one incident by URL, domain, or subject value. Subject is URL-encoded. It is categorised as a Read tool in the Phishfort MCP Server, which means it retrieves data without modifying state.
Register the Phishfort MCP server in PolicyLayer and add a rule for phishfort_find_incident_by_subject: 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.
phishfort_find_incident_by_subject is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the phishfort_find_incident_by_subject 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.
Set action: deny in the PolicyLayer policy for phishfort_find_incident_by_subject. 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.
phishfort_find_incident_by_subject 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.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →