get_dashboard_url

Return the local dashboard URL.

SERVERLocalAnt SOURCEyuga-hashimoto/localant

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/yuga-hashimoto-localant/get-dashboard-url.md

WHAT IT DOES

What get_dashboard_url does on LocalAnt

AI agents call get_dashboard_url to retrieve information from LocalAnt 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_url is rated Low

This tool retrieves and returns a URL string—a read-only query operation. It does not modify, execute, or delete anything. The dashboard URL is configuration/metadata information. Even if an agent obtains this URL, visiting it poses no direct risk via this tool alone. Severity is low because the information returned is likely non-sensitive routing data for a local service.

From the tool's definition Tool name is 'get_dashboard_url' and description states 'Return the local dashboard URL.' The verb 'return' indicates data retrieval with no side effects.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs get_dashboard_url safely

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

get_dashboard_url Allowed

get_dashboard_url 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_url": {}
  }
}

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

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

FAQ

Questions about get_dashboard_url

What does the get_dashboard_url tool do? +

Return the local dashboard URL. It is categorised as a Read tool in the LocalAnt MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_dashboard_url? +

Register the LocalAnt MCP server in PolicyLayer and add a rule for get_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 LocalAnt. Nothing to install.

What risk level is get_dashboard_url? +

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

Can I rate-limit get_dashboard_url? +

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

How do I block get_dashboard_url completely? +

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

What MCP server provides get_dashboard_url? +

get_dashboard_url is provided by the LocalAnt MCP server (yuga-hashimoto/localant). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on LocalAnt, and thousands of servers like it.

This server

All 216 LocalAnt 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 →