Port forward a Kubernetes service to a local port
AI agents invoke port-forward to trigger actions in Kubernetes MCP Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
Port-forwarding is an active operation that spawns a background process and opens a network connection, enabling external access to internal cluster services. It is not a simple read/query, but an execution of an ongoing network operation. Misuse could expose internal services to unintended access, hence medium severity.
From the tool's definition 'Port forward a Kubernetes service to a local port' — actively establishes a network tunnel/process that routes traffic between local and cluster resources
Attacks that exploit this kind of access
Port forward a Kubernetes service to a local port. It is categorised as a Execute tool in the Kubernetes MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Kubernetes MCP Server MCP server in PolicyLayer and add a rule for port-forward: 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. Nothing to install.
port-forward is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the port-forward 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 port-forward. 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.
port-forward is provided by the Kubernetes MCP Server MCP server (thekaranpargaie/kube-mcp). 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 →