get_dashboard_config

Get Lovelace dashboard config. url_path can be a dashboard (e.g. 'map') or a view path

SERVERHa Nexus Agent SOURCEfistacho/ha-nexus-agent

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/fistacho-ha-nexus-agent/get-dashboard-config.md

WHAT IT DOES

What get_dashboard_config does on Ha Nexus Agent

AI agents call get_dashboard_config to retrieve information from Ha Nexus Agent without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why get_dashboard_config is rated Low

This tool retrieves and queries Lovelace dashboard configuration without side effects or data modification. It is a straightforward read operation that fetches existing dashboard settings based on the provided url_path parameter.

From the tool's definition Tool name 'get_dashboard_config' and description 'Get Lovelace dashboard config' indicate retrieval of dashboard configuration data with no modification capability.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs get_dashboard_config safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Ha Nexus Agent, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_dashboard_config, this is the rule to start with:

get_dashboard_config Allowed

get_dashboard_config is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_dashboard_config": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Ha Nexus Agent, apply this rule, and every get_dashboard_config call is checked against it from then on.

FAQ

Questions about get_dashboard_config

What does the get_dashboard_config tool do? +

Get Lovelace dashboard config. url_path can be a dashboard (e.g. 'map') or a view path. It is categorised as a Read tool in the Ha Nexus Agent MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_dashboard_config? +

Register the Ha Nexus Agent MCP server in PolicyLayer and add a rule for get_dashboard_config: 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 Ha Nexus Agent. Nothing to install.

What risk level is get_dashboard_config? +

get_dashboard_config is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_dashboard_config? +

Yes. Add a rate_limit block to the get_dashboard_config 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.

How do I block get_dashboard_config completely? +

Set action: deny in the PolicyLayer policy for get_dashboard_config. 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.

What MCP server provides get_dashboard_config? +

get_dashboard_config is provided by the Ha Nexus Agent MCP server (fistacho/ha-nexus-agent). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Ha Nexus Agent, and thousands of servers like it.

This server

All 276 Ha Nexus Agent tools →

Across the catalogue

get_cocktail_by_category on Cocktails RAG MCP Server →get_torrent_detail on M-Team MCP Server →aiva_get_affiliate on AIVA MCP Server →get-chuck-categories on Jokes MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →