Get detailed Windows Firewall status with all profile settings
AI agents call firewall_status_detailed to retrieve information from Mcp Windows without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and retrieves firewall configuration information without making any changes to system state. It is a read-only operation that gathers status data for inspection purposes. The low severity reflects minimal risk even if an AI misuses it—the worst outcome would be information disclosure about firewall configuration, not system compromise or data loss.
From the tool's definition Tool name 'firewall_status_detailed' and description 'Get detailed Windows Firewall status with all profile settings' indicate pure information retrieval with no modification, execution, or deletion of data.
Documented attack patterns abuse exactly the kind of access firewall_status_detailed gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Mcp Windows, and nothing reaches the server without passing your rules. This is the rule we recommend for firewall_status_detailed:
{
"version": "1",
"default": "deny",
"tools": {
"firewall_status_detailed": {}
}
}firewall_status_detailed is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Get detailed Windows Firewall status with all profile settings. It is categorised as a Read tool in the Mcp Windows MCP Server, which means it retrieves data without modifying state.
Register the Mcp Windows MCP server in PolicyLayer and add a rule for firewall_status_detailed: 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 Mcp Windows. Nothing to install.
firewall_status_detailed 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 firewall_status_detailed 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 firewall_status_detailed. 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.
firewall_status_detailed is provided by the Mcp Windows MCP server (mukul975/mcp-windows-automation). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 441 Mcp Windows tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
441 Mcp Windows tools catalogued and risk-classified — across an index of 42,500+ MCP servers.