Get detailed status and diagnostics of the webhook tunnel connection. Returns comprehensive information about the tunnel provider, connection status, public URL, health monitoring, and execution context detection. Useful for: - Troubleshooting connectivity issues - Verifying tunnel is active befo...
AI agents call get_tunnel_status to retrieve information from BNB Chain MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a pure diagnostic/status query tool. It retrieves and reports information about an existing tunnel connection without modifying, deleting, or triggering financial operations. No arguments are mentioned that would permit code execution or data mutation. The tool is informational only, making it a Read category with low severity.
From the tool's definition Tool name 'get_tunnel_status' and description states it 'Get detailed status and diagnostics' and 'Returns comprehensive information' about tunnel connection, provider, and health monitoring.
Documented attack patterns abuse exactly the kind of access get_tunnel_status gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and BNB Chain MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for get_tunnel_status:
{
"version": "1",
"default": "deny",
"tools": {
"get_tunnel_status": {}
}
}get_tunnel_status is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Get detailed status and diagnostics of the webhook tunnel connection. Returns comprehensive information about the tunnel provider, connection status, public URL, health monitoring, and execution context detection. Useful for: - Troubleshooting connectivity issues - Verifying tunnel is active before creating payments - Understanding which provider is being used (ngrok, zrok, or manual) - Checking if auto-reconnect is working - Seeing detected execution context (N8N, Opal, VPS, Docker, local) Connection statuses: - disconnected: Tunnel not started - connecting: Tunnel is initializing - connected: Tunnel is active and healthy - reconnecting: Tunnel lost connection and is attempting to reconnect - error: Tunnel failed after max reconnection attempts No input parameters required - returns current status immediately. It is categorised as a Read tool in the BNB Chain MCP MCP Server, which means it retrieves data without modifying state.
Register the BNB Chain 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 BNB Chain MCP. Nothing to install.
get_tunnel_status 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_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.
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.
get_tunnel_status is provided by the BNB Chain MCP server (nirholas/bnbchain-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 1240 BNB Chain MCP tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
1240 BNB Chain MCP tools catalogued and risk-classified — across an index of 42,500+ MCP servers.