No user-submitted related servers found.
Scored across 368 tools
Many tools are duplicated for firewall vs NAT policy operations (e.g., deploy, preview, cleanup, selective_deploy), and the descriptions clearly delineate the difference, but there are also tools like get_policy_deploy_job vs get_policy_deploy_job_device_status vs get_template_deploy_status that could be confused. Also, there are many list_* tools that follow a pattern but the sheer number of similar profile types (e.g., anti_virus, flow_based_antivirus, content_filtering, enhanced_content_filtering) may cause misselection.
The tool names are consistently formatted as sdcloud_<verb>_<resource> in snake_case, with verbs like list, get, create, update, delete, deploy, preview, start_, get_* for job statuses. There are some deviations such as 'bulk_create_device' vs 'create_device' and 'remove_devices' vs 'delete_device', but overall the pattern is predictable and consistent.
With 368 tools, the server is extremely comprehensive for an enterprise security management platform, but the sheer volume far exceeds the typical well-scoped MCP server (3-15 tools). While each tool may cover a distinct API endpoint, the count is excessive and would overwhelm an agent, making it difficult to select the right tool efficiently.
The tool surface covers full CRUD for many object types (e.g., addresses, profiles, policies, users, sites, templates, etc.), includes lifecycle operations like deploy, preview, cleanup, and status polling for async jobs, and also provides read-only reference data (IPS contexts, services, vulnerabilities) and settings singletons. The coverage is exceptionally complete for the security director cloud domain.