AI agents call phishfort_get_incident 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 a single incident record from PhishFort by its identifier. It performs a query operation with no side effects—it does not create, modify, delete, or execute any actions. The blast radius of misuse is minimal: an agent could only read incident data that the authenticated user is already authorized to access. No financial, destructive, or irreversible operations are possible.
From the tool's definition Tool name 'phishfort_get_incident' and description 'Get one PhishFort incident by id' indicate a retrieval operation. The verb 'Get' and the read-only nature of querying an incident by identifier with no modification or execution implied.
Attacks that exploit this kind of access
Get one PhishFort incident by id. 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_get_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.
phishfort_get_incident 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_get_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.
Set action: deny in the PolicyLayer policy for phishfort_get_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.
phishfort_get_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.
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 →