AI agents call phishfort_verify_webhook_signature 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.
Webhook signature verification is a security validation operation that inspects incoming data to confirm its authenticity. This is a read-only operation with no side effects on data or systems. The tool accepts a signature string and secret, compares them cryptographically, and returns a boolean or validation result.
From the tool's definition The tool description indicates it 'Verify[ies] X-PhishFort-Signature' - a verification/validation operation that checks a cryptographic signature without modifying, deleting, or executing external operations. It reads and validates data.
Attacks that exploit this kind of access
Verify X-PhishFort-Signature. Prefer secret_file inside PHISHFORT_SECRET_DIR. 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_verify_webhook_signature: 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_verify_webhook_signature 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_verify_webhook_signature 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_verify_webhook_signature. 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_verify_webhook_signature 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 →