Plan infrastructure deployment changes
AI agents invoke iac_plan_deployment 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.
Planning a deployment on a firewall/network management server typically involves executing logic against live infrastructure state (e.g., computing diffs, staging changes). While it may not commit changes, it executes an operation with non-trivial side effects or exposure risk on critical network security infrastructure.
From the tool's definition 'Plan infrastructure deployment changes' — planning a deployment implies executing a dry-run or evaluation process that may interact with live firewall infrastructure to calculate and stage changes
Documented attack patterns abuse exactly the kind of access iac_plan_deployment 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 iac_plan_deployment:
{
"version": "1",
"default": "deny",
"tools": {
"iac_plan_deployment": {
"limits": [
{
"counter": "iac_plan_deployment_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}iac_plan_deployment 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.
Plan infrastructure deployment changes. 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 iac_plan_deployment: 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.
iac_plan_deployment 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 iac_plan_deployment 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 iac_plan_deployment. 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.
iac_plan_deployment 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.