Add an IP address to the Fail2Ban whitelist
AI agents use plesk_fail2ban_whitelist_ip to create or update resources in Plesk MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Plesk MCP Server environment.
This tool modifies Fail2Ban configuration by adding an IP to the whitelist, which is a reversible write operation. However, the severity is high because misconfiguration could disable critical security protections—whitelisting a malicious IP would bypass intrusion detection.
From the tool's definition Tool name 'plesk_fail2ban_whitelist_ip' and description 'Add an IP address to the Fail2Ban whitelist' indicate the tool creates or modifies security whitelist entries.
Attacks that exploit this kind of access
Add an IP address to the Fail2Ban whitelist. It is categorised as a Write tool in the Plesk MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Plesk MCP Server MCP server in PolicyLayer and add a rule for plesk_fail2ban_whitelist_ip: 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 Plesk MCP Server. Nothing to install.
plesk_fail2ban_whitelist_ip is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the plesk_fail2ban_whitelist_ip 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 plesk_fail2ban_whitelist_ip. 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.
plesk_fail2ban_whitelist_ip is provided by the Plesk MCP Server MCP server (klan1/plesk-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 →