tcp_write

Write data to an open TCP session.

SERVERJshookmcp SOURCE@jshookmcp/jshook

High RISK CLASS

Category Execute

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-vmoranv-jshookmcp/tcp-write.md

WHAT IT DOES

What tcp_write does on Jshookmcp

AI agents invoke tcp_write to trigger actions in Jshookmcp. 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.

RISK

Why tcp_write is rated High

Sending arbitrary data over TCP can trigger external operations with unpredictable effects.

From the tool's definition Write data to an open TCP session

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs tcp_write safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Jshookmcp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For tcp_write, this is the rule to start with:

tcp_write Rate-limited

tcp_write 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": {
    "tcp_write": {
      "limits": [
        {
          "counter": "tcp_write_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Jshookmcp, apply this rule, and every tcp_write call is checked against it from then on.

FAQ

Questions about tcp_write

What does the tcp_write tool do? +

Write data to an open TCP session. It is categorised as a Execute tool in the Jshookmcp MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on tcp_write? +

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

What risk level is tcp_write? +

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

Can I rate-limit tcp_write? +

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

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

tcp_write is provided by the Jshook MCP server (@jshookmcp/jshook). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Jshook, and thousands of servers like it.

This server

All 736 Jshook tools → High-risk tools on this server →

Across the catalogue

All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →