Add inbound links and polish rate limiting guide

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

Author: jerm-dro

docs/toolhive/guides-k8s/auth-k8s.mdx

@@ -901,6 +901,8 @@ kubectl logs -n toolhive-system -l app.kubernetes.io/name=weather-server-k8s
 
 ## Next steps
 
+- [Configure rate limiting](./rate-limiting.mdx) to set per-user and shared
+  request limits on MCP servers
 - [Configure token exchange](./token-exchange-k8s.mdx) to let MCP servers
   authenticate to backend services
 - [Set up audit logging](./logging.mdx) to track authentication decisions and

docs/toolhive/guides-k8s/intro.mdx

@@ -99,4 +99,5 @@ Once the operator is installed, you can create and manage MCP servers:
 
 - [Run MCP servers in Kubernetes](./run-mcp-k8s.mdx)
 - [Proxy remote MCP servers](./remote-mcp-proxy.mdx)
+- [Rate limiting](./rate-limiting.mdx)
 - [Virtual MCP Server (vMCP)](../guides-vmcp/index.mdx)

docs/toolhive/guides-k8s/rate-limiting.mdx

@@ -23,8 +23,8 @@ request must pass all applicable limits to proceed.
 Before you begin, ensure you have:
 
 - A Kubernetes cluster with the ToolHive Operator installed
-- Redis deployed for session storage (rate limiting uses Redis as its counter
-  backend)
+- Redis deployed for session storage (rate limiting uses Redis to store token
+  bucket counters)
 - For per-user limits: authentication enabled on the MCPServer (`oidcConfig`,
   `oidcConfigRef`, or `externalAuthConfigRef`)
 
@@ -65,9 +65,9 @@ total throughput to protect downstream services.
 apiVersion: toolhive.stacklok.dev/v1alpha1
 kind: MCPServer
 metadata:
-  name: my-server
+  name: weather-server
 spec:
-  image: my-mcp-server:latest
+  image: ghcr.io/stackloklabs/weather-mcp/server
   transport: streamable-http
   sessionStorage:
     provider: redis
@@ -94,9 +94,9 @@ users by the `sub` claim from their JWT token.
 apiVersion: toolhive.stacklok.dev/v1alpha1
 kind: MCPServer
 metadata:
-  name: my-server
+  name: weather-server
 spec:
-  image: my-mcp-server:latest
+  image: ghcr.io/stackloklabs/weather-mcp/server
   transport: streamable-http
   oidcConfig:
     type: inline
@@ -126,9 +126,9 @@ throughput.
 apiVersion: toolhive.stacklok.dev/v1alpha1
 kind: MCPServer
 metadata:
-  name: my-server
+  name: weather-server
 spec:
-  image: my-mcp-server:latest
+  image: ghcr.io/stackloklabs/weather-mcp/server
   transport: streamable-http
   oidcConfig:
     type: inline

docs/toolhive/guides-k8s/redis-session-storage.mdx

@@ -12,8 +12,10 @@ when pods restart and users must re-authenticate. Redis Sentinel provides
 persistent storage with automatic master discovery, ACL-based access control,
 and optional failover when replicas are configured.
 
-Redis session storage is also required for horizontal scaling when running
-multiple [MCPServer](./run-mcp-k8s.mdx#horizontal-scaling) or
+Redis is also required as the backend for [rate limiting](./rate-limiting.mdx),
+which stores token bucket counters in Redis independently of session data. It is
+also required for horizontal scaling when running multiple
+[MCPServer](./run-mcp-k8s.mdx#horizontal-scaling) or
 [VirtualMCPServer](../guides-vmcp/scaling-and-performance.mdx#session-storage-for-multi-replica-deployments)
 replicas, so that sessions are shared across pods.