Skip to main content
Glama
Symantec Data Center Security AIops

Symantec Data Center Security AIops

by AIops-tools

Related Servers

Alternatives to Symantec Data Center Security AIops

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables governed, read-only investigations of on-premises endpoint incidents and events, entities, threat feeds, policy lists, and sandbox results through audited MCP and CLI calls.
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables secure, read-only-by-default inspection and auditing of load balancers, WAF, policies, bot defense, API security, security events, and logs, with planned human-confirmed writes for selected configuration changes and no deletions.
      MIT
    • A
      license
      Not graded
      quality
      A
      maintenance
      Enables investigation of devices, model breaches and analyst incidents from an MCP host through a bounded set of read-only tools, with operator-controlled profiles and a fixed operation inventory. Writes, PCAP export, email and HTTP transport are excluded, and responses are minimized and escaped before entering model context.
      17 npm
      2
      Apache 2.0
    • A
      license
      A
      quality
      B
      maintenance
      Enables read-only lookup and analysis of SaaS applications, transactions, invoices, spend, renewals, and people, including spend summaries, upcoming renewals, and missing-invoice checks, through an MCP client.
      7
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables read-only access to CloudSOC DLP incidents, profiles, detection patterns, data identifiers, and index health through governed MCP tools with local audit logging.
      MIT
    • F
      license
      Not graded
      quality
      C
      maintenance
      Enables read-only access to managed network devices over SSH or Telnet via MCP, allowing users to probe devices, retrieve redacted running or startup configs, gather facts and interfaces, back up multiple devices, and compare configs for drift or unsaved changes.
      -

    TDQS

    C2.5/5.0

    Scored across 35 tools

    Disambiguation3/5

    Bare nouns force the agent to infer a singular=read-one / plural=list convention (dcs_policy vs dcs_policies, dcs_role vs dcs_roles), which the terse descriptions only partially clarify. Clusters like dcs_alerts / dcs_alert_rules / dcs_alert_stats / dcs_alert_details / dcs_alert_notifications, and dcs_tags vs dcs_asset_tags, have fuzzy boundaries that invite misselection.

    Naming Consistency4/5

    Every tool uses the same dcs_ prefix and snake_case, and the singular/plural convention for get-vs-list is applied consistently across policies, roles, report jobs, and security groups. Minor deviations (dcs_status, dcs_syslogs) and the absence of explicit verbs keep it from a 5.

    Tool Count2/5

    35 tools is heavy for a single server, and several are marginal variants of the same resource (dcs_policy_settings, dcs_policy_library, dcs_alert_details, dcs_alert_notifications, dcs_report_stats). The domain is broad, but the surface feels padded rather than curated.

    Completeness3/5

    Read coverage is genuinely broad — assets, alerts, events, policies, reports, RBAC, security groups, tags, syslog, licenses, users. However, the surface is entirely read-only, with no create/update/delete or policy-assignment operations for any managed resource, which is a notable gap if this is meant to drive an ops workflow rather than pure observability.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues