fiveg_nf_status
AI agents call fiveg_nf_status to retrieve information from Kubernetes MCP Server – 5G Core Edition without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Despite empty description, contextual evidence from sibling tools and naming convention strongly suggests this retrieves/queries 5G NF operational status. No side effects indicated. Classified as Read with medium severity because exposing 5G core network state to an AI agent could enable reconnaissance or inform attacks on critical telecom infrastructure, though the tool itself performs no harmful action.
From the tool's definition Tool name 'fiveg_nf_status' suggests querying 5G Network Function (NF) status information. Sibling tools on the server (fiveg_core_topology, fiveg_health_check, fiveg_slice_info, k8s_describe_pod, k8s_get_*) are all read-only query operations.
Attacks that exploit this kind of access
fiveg_nf_status. It is categorised as a Read tool in the Kubernetes MCP Server – 5G Core Edition MCP Server, which means it retrieves data without modifying state.
Register the Kubernetes MCP Server – 5G Core Edition MCP server in PolicyLayer and add a rule for fiveg_nf_status: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches Kubernetes MCP Server – 5G Core Edition. Nothing to install.
fiveg_nf_status is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the fiveg_nf_status rule in your PolicyLayer policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.
Set action: deny in the PolicyLayer policy for fiveg_nf_status. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.
fiveg_nf_status is provided by the Kubernetes MCP Server – 5G Core Edition MCP server (sanzco/mcp5g). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →