tunnels_list
Read tunnels.list through the Appaloft application operation catalog. Shared with CLI and HTTP/API.
This record as markdown: /tools/appaloft-mcp/tunnels-list.md
What tunnels_list does on Appaloft
AI agents call tunnels_list to retrieve information from Appaloft without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
status | string | — |
Parameters from the server's own tool schema.
Why tunnels_list is rated Low
This tool queries and lists tunnels from the Appaloft application, a standard read/retrieval operation. No data is created, modified, deleted, or external processes triggered. The blast radius of misuse is low—an agent gaining unauthorized tunnel visibility could leak infrastructure details, but cannot cause direct damage. Classified as Read with low severity.
From the tool's definition Tool name 'tunnels_list' and description explicitly states 'Read tunnels.list' — retrieves tunnel information without modification or side effects.
Attacks that exploit this kind of access
The rule that runs tunnels_list safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Appaloft, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For tunnels_list, this is the rule to start with:
tunnels_list 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 Appaloft, apply this rule, and every tunnels_list call is checked against it from then on.
Questions about tunnels_list
Read tunnels.list through the Appaloft application operation catalog. Shared with CLI and HTTP/API. It is categorised as a Read tool in the Appaloft MCP Server, which means it retrieves data without modifying state.
tunnels_list accepts 1 parameter: status. The full parameter table on this page comes from the server's own tool schema.
Register the Appaloft MCP server in PolicyLayer and add a rule for tunnels_list: 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 Appaloft. Nothing to install.
tunnels_list 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 tunnels_list 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 tunnels_list. 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.
tunnels_list is provided by the Appaloft MCP server (@appaloft/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Appaloft, and thousands of servers like it.
This server
Across the catalogue