mcpField
S
Symantec ZTNA AIops

Symantec ZTNA AIops

Local
github.com/AIops-toolsSecurity0Updated 5d ago
Repository

About Symantec ZTNA AIops

Symantec ZTNA AIops is an independent MCP server, CLI, and skill for Symantec Zero Trust Network Access. Its preview provides 40 governed read-only tools for tenant health, applications, policies, identities, integrations, and audit logs.

Key features

  1. 0140 governed read-only tools
  2. 02Tenant and connector health queries
  3. 03Application and access-policy operations
  4. 04Identity, DNS, and cloud-integration queries
  5. 05Audit-log searches with pagination

Use cases

  1. 01Review tenant and connector health
  2. 02Inspect applications and access policies
  3. 03Search identities, integrations, and audit logs

MCP support

Exposes 40 read-only Symantec ZTNA operations to MCP clients. Its CLI commands mirror the MCP tools; the preview exposes no state-changing API.

Configuration

Local server config is the same for every client. Copy it into your client’s MCP config file.

mcp.json · Universal config
{
  "mcpServers": {
    "aiops-tools-symantec-ztna-aiops": {
      "command": "uvx",
      "args": [
        "symantec-ztna-aiops"
      ]
    }
  }
}
Run commanduvx symantec-ztna-aiops

Local servers need a runtime on your machine (e.g. Node.js 18+). Config file locations differ by client; see your client’s docs.

Packages
pypisymantec-ztna-aiops0.1.0

Tools

40

Saved tool list · updated 5d ago

ParameterTypeRequiredDescription
pageintegerNo
limitintegerNo
filter_textstringNo

Details

From the project README

Symantec ZTNA AIops

An independent MCP server, CLI and skill for Symantec Zero Trust Network Access. This preview exposes 40 governed read tools for tenant and connector health, applications, access policies, shared objects, collections, DNS, identities, cloud integrations and audit logs. It is separate from SEP, SES Cloud and on-premises EDR.

Community-maintained project. Not affiliated with or endorsed by Broadcom or Symantec; product names are their owners’ trademarks.

Setup

Set SYMANTEC_ZTNA_URL to the tenant API HTTPS origin, such as https://api.example.luminatesec.com, and provide SYMANTEC_ZTNA_CLIENT_ID and SYMANTEC_ZTNA_CLIENT_SECRET from a ZTNA API client. The URL must be an origin without a path. Optional settings are SYMANTEC_ZTNA_CA_BUNDLE, SYMANTEC_ZTNA_TIMEOUT and SYMANTEC_ZTNA_AIOPS_HOME for local governance storage. Use an API client with the least privileges needed for the reads you intend to call.

Run uv run symantec-ztna-aiops --help. The MCP entry point is symantec-ztna-aiops-mcp. CLI commands mirror all MCP tools; see the operations catalog for the full list and official API sources.

Paged endpoints return truncated, nextPage and totalReported from the documented server page metadata. Audit searches fetch one extra log to measure truncation and return the next SearchAfterValues cursor. Search windows are capped at 30 days; connector metrics at seven days. health-sample is explicitly a sample and reports partial probe failures. No state-changing API is exposed in this unverified preview.

See verification for official API evidence and the remaining live-tenant checks. Missing a common ZTNA task? Open an issue or PR with the product version and a sanitized response shape.

Comments

Markdown supported

New to MCP?

From what the protocol is to installing your first server, these answers cover most first questions.

An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.