send_command_by_path · PyNet Bridge MCP: Risk & Policy

WHAT IT DOES

What send_command_by_path does on PyNet Bridge

AI agents invoke send_command_by_path to trigger actions in PyNet Bridge. 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 send_command_by_path needs a policy

This tool executes a script file by path in an external engine. The effects depend entirely on the script's content, which could range from benign reads to destructive operations. Since it triggers arbitrary script execution in the PyNet engine, it falls squarely in the Execute category.

From the tool's definition "Executes a script file directly by path in the PyNet engine" — the tool runs an external script file in the PyNet engine

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

send_command_by_path Rate-limited

send_command_by_path 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": {
    "send_command_by_path": {
      "limits": [
        {
          "counter": "send_command_by_path_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 PyNet Bridge, so you can run agents against it safely.

FAQ

Questions about send_command_by_path

What does the send_command_by_path tool do? +

Executes a script file directly by path in the PyNet engine, without sending content inline. It is categorised as a Execute tool in the PyNet Bridge MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on send_command_by_path? +

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

What risk level is send_command_by_path? +

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

Can I rate-limit send_command_by_path? +

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

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

send_command_by_path is provided by the PyNet Bridge MCP server (rafael-nunezdearenas/pynetbridge). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.