get_tunnel_status

Return the current tunnel provider and status.

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-tunnel-status.md

WHAT IT DOES

What get_tunnel_status does on LocalAnt

AI agents call get_tunnel_status 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_tunnel_status is rated Low

This tool queries and returns tunnel status without creating, modifying, executing, or deleting anything. It is a simple information retrieval operation with no side effects. The low severity reflects minimal risk even if an agent queries this repeatedly—it only reads state without operational impact.

From the tool's definition Tool name and description indicate retrieval of status information ('Return the current tunnel provider and status') with no modification or execution capabilities.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs get_tunnel_status 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_tunnel_status, this is the rule to start with:

get_tunnel_status Allowed

get_tunnel_status 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_tunnel_status": {}
  }
}

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_tunnel_status call is checked against it from then on.

FAQ

Questions about get_tunnel_status

What does the get_tunnel_status tool do? +

Return the current tunnel provider and status. 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_tunnel_status? +

Register the LocalAnt MCP server in PolicyLayer and add a rule for get_tunnel_status: 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_tunnel_status? +

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

Can I rate-limit get_tunnel_status? +

Yes. Add a rate_limit block to the get_tunnel_status 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_tunnel_status completely? +

Set action: deny in the PolicyLayer policy for get_tunnel_status. 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_tunnel_status? +

get_tunnel_status 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_task_status on 0rca Dojo MCP Server →get_cocktail_by_category on Cocktails RAG MCP Server →get_torrent_detail on M-Team MCP Server →aiva_get_affiliate on AIVA MCP Server → The MCP Attack Database →

Guides

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