get_services

What get_services does on Ncp

AI agents call get_services to retrieve information from Ncp without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Why get_services is rated Low

This tool performs a straightforward enumeration/listing operation. It retrieves metadata about services in a Kubernetes-style namespace context with no ability to modify, delete, or execute actions. The read-only nature and low blast radius if misused by an agent (worst case: information disclosure about available services) place it firmly in the Read category with low severity.

From the tool's definition Tool name 'get_services' and description 'List services in namespace' indicate a query operation that retrieves information about services without modification or side effects.

The rule that runs get_services safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Ncp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_services, this is the rule to start with:

{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_services": {}
  }
}

Questions about get_services