fiveg_slice_info
AI agents call fiveg_slice_info 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.
The tool appears designed to retrieve information about 5G network slices, consistent with other query-style tools on the server. However, confidence is moderate (0.72) because the description is empty, leaving some ambiguity about exact behavior and potential side effects.
From the tool's definition Tool name 'fiveg_slice_info' suggests retrieval of network slice information; sibling tools (fiveg_core_topology, fiveg_health_check, fiveg_nf_status, k8s_describe_pod, k8s_get_*) are uniformly Read-pattern tools that query cluster and 5G state without…
Attacks that exploit this kind of access
fiveg_slice_info. 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_slice_info: 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_slice_info 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_slice_info 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_slice_info. 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_slice_info 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 →