shimmy-tool-opnsense-mcp-read-only

Setting up read-only OPNsense MCP access requires preserving distinct Podman secrets and validating the read-only API endpoint path. This Skill provides workflow guidance to ensure strict API privilege boundaries are maintained during Shimmy tool maintenance.

A read-only OPNsense MCP workflow is a context-first operational process that guides safe Shimmy tool maintenance and usage. It enforces API privilege boundaries and validates endpoint paths to prevent unauthorized configuration changes.

Yes, you need distinct Podman secrets for OPNsense MCP read-only endpoints. Preserving separate secret configurations is required to maintain API privilege boundaries and ensure safe context-first tool operations.

You validate the OPNsense MCP read-only endpoint path by running stdio smoke validations. This process confirms that the API privilege boundaries are correctly configured and the read-only access is functioning as intended.

Yes, this approach applies to version-specific OPNsense MCP guidance review. It keeps operational guidance close to the tool, ensuring maintenance and usage stay consistent across different versions of the Shimmy tool.

Your OPNsense MCP workflow might use the wrong endpoints if distinct Podman secrets are not preserved and the read-only API validation path is not properly checked. This Skill guides context-first operations to prevent such misconfigurations.