proxychains_test · Proxychains MCP Server MCP: Risk & Policy

WHAT IT DOES

What proxychains_test does on Proxychains MCP Server

AI agents invoke proxychains_test to trigger actions in Proxychains MCP Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.

WHY IT NEEDS A POLICY

Why proxychains_test needs a policy

This tool executes network connectivity tests through proxy chains on a remote system, which constitutes running external operations whose effects depend on arguments (e.g., target host). It is not a simple read/query of local data — it initiates outbound network connections. Misuse could probe internal or external targets through proxies, enabling reconnaissance, but it does not modify data or move money.

From the tool's definition 'Test the proxy chain by checking connectivity and measuring latency' — triggers active network connectivity tests and latency measurements against external targets via SSH on a remote Linux host

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

proxychains_test Rate-limited

proxychains_test stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "proxychains_test": {
      "limits": [
        {
          "counter": "proxychains_test_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Proxychains MCP Server, so you can run agents against it safely.

FAQ

Questions about proxychains_test

What does the proxychains_test tool do? +

Test the proxy chain by checking connectivity and measuring latency. Optionally test against a specific target. It is categorised as a Execute tool in the Proxychains MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on proxychains_test? +

Register the Proxychains MCP Server MCP server in PolicyLayer and add a rule for proxychains_test: 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 Proxychains MCP Server. Nothing to install.

What risk level is proxychains_test? +

proxychains_test is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit proxychains_test? +

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

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

proxychains_test is provided by the Proxychains MCP Server MCP server (schwarztim/sec-proxychains-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.