AI agents invoke ids_block_ip to trigger actions in OPNSense MCP Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
This tool triggers an active firewall/IDS enforcement action — blocking an IP address. While it modifies network policy (Write-like), the primary effect is executing an external operation on the firewall that immediately affects network traffic. It is not easily reversible in an automated sense (a blocked IP requires explicit unblocking), but it's not purely destructive data deletion.
From the tool's definition Block an IP address detected by IDS
Documented attack patterns abuse exactly the kind of access ids_block_ip gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and OPNSense MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for ids_block_ip:
{
"version": "1",
"default": "deny",
"tools": {
"ids_block_ip": {
"limits": [
{
"counter": "ids_block_ip_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}ids_block_ip stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Block an IP address detected by IDS. It is categorised as a Execute tool in the OPNSense MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the OPNSense MCP Server MCP server in PolicyLayer and add a rule for ids_block_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 OPNSense MCP Server. Nothing to install.
ids_block_ip is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the ids_block_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 ids_block_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.
ids_block_ip is provided by the OPNSense MCP Server MCP server (vespo92/opnsensemcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 196 OPNSense MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
196 OPNSense MCP Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.