get_kubernetes_dashboard_url
Get the dashboard URL for a Kubernetes cluster
This record as markdown: /tools/takashito-linode-mcp-server/get-kubernetes-dashboard-url.md
What get_kubernetes_dashboard_url does on Linode MCP Server
AI agents call get_kubernetes_dashboard_url to retrieve information from Linode MCP Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why get_kubernetes_dashboard_url is rated Low
This tool performs a simple information retrieval operation—fetching a dashboard URL for an existing Kubernetes cluster. It has no side effects, does not modify infrastructure, and does not execute code or commands. The misuse risk is minimal, as obtaining a URL alone does not grant unauthorized access or enable destructive actions without additional independent actions by an attacker.
From the tool's definition Tool name 'get_kubernetes_dashboard_url' and description 'Get the dashboard URL for a Kubernetes cluster' indicate a retrieval operation that returns a URL without modifying any resources or executing operations.
Attacks that exploit this kind of access
The rule that runs get_kubernetes_dashboard_url safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Linode MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_kubernetes_dashboard_url, this is the rule to start with:
get_kubernetes_dashboard_url is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Linode MCP Server, apply this rule, and every get_kubernetes_dashboard_url call is checked against it from then on.
Questions about get_kubernetes_dashboard_url
Get the dashboard URL for a Kubernetes cluster. It is categorised as a Read tool in the Linode MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Linode MCP Server MCP server in PolicyLayer and add a rule for get_kubernetes_dashboard_url: 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 Linode MCP Server. Nothing to install.
get_kubernetes_dashboard_url 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 get_kubernetes_dashboard_url 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 get_kubernetes_dashboard_url. 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.
get_kubernetes_dashboard_url is provided by the Linode MCP Server MCP server (takashito/linode-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Linode MCP Server, and thousands of servers like it.
This server
Across the catalogue