Low Risk

tcp_proxy_list

[API] List all TCP proxies for a service in a specific environment ⚡️ Best for: ✓ Viewing TCP proxy configurations ✓ Managing external access ✓ Auditing service endpoints → Prerequisites: service_list → Next steps: tcp_proxy_create → Related: domain_list, service_info

Single-target operation

Part of the Railway MCP Server MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.

AI agents call tcp_proxy_list to retrieve information from Railway MCP Server without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.

Even though tcp_proxy_list only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.

Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.

jason-tan-swe-railway-mcp.yaml
tools:
  tcp_proxy_list:
    rules:
      - action: allow

See the full Railway MCP Server policy for all 38 tools.

Tool Name tcp_proxy_list
Category Read
Risk Level Low

View all 38 tools →

Agents calling read-class tools like tcp_proxy_list have been implicated in these attack patterns. Read the full case and prevention policy for each:

Browse the full MCP Attack Database →

Other tools in the Read risk category across the catalogue. The same policy patterns (rate-limit, allow) apply to each.

What does the tcp_proxy_list tool do? +

[API] List all TCP proxies for a service in a specific environment ⚡️ Best for: ✓ Viewing TCP proxy configurations ✓ Managing external access ✓ Auditing service endpoints → Prerequisites: service_list → Next steps: tcp_proxy_create → Related: domain_list, service_info. It is categorised as a Read tool in the Railway MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on tcp_proxy_list? +

Add a rule in your Intercept YAML policy under the tools section for tcp_proxy_list. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Railway MCP Server MCP server.

What risk level is tcp_proxy_list? +

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

Can I rate-limit tcp_proxy_list? +

Yes. Add a rate_limit block to the tcp_proxy_list rule in your Intercept 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 tcp_proxy_list completely? +

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

What MCP server provides tcp_proxy_list? +

tcp_proxy_list is provided by the Railway MCP Server MCP server (jason-tan-swe/railway-mcp). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policies on Railway MCP Server

Open source. One binary. Zero dependencies.

npx -y @policylayer/intercept
github.com/policylayer/intercept →
// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.