tls_read_until

Read from an open TLS session until a delimiter or byte limit is reached.

SERVERJshookmcp SOURCE@jshookmcp/jshook

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-vmoranv-jshookmcp/tls-read-until.md

WHAT IT DOES

What tls_read_until does on Jshookmcp

AI agents call tls_read_until to retrieve information from Jshookmcp without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why tls_read_until is rated Low

Retrieves data from an established TLS connection without modification or execution.

From the tool's definition Read from an open TLS session until delimiter or byte limit reached.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs tls_read_until 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 tls_read_until, this is the rule to start with:

tls_read_until Allowed

tls_read_until is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "tls_read_until": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about tls_read_until

What does the tls_read_until tool do? +

Read from an open TLS session until a delimiter or byte limit is reached. It is categorised as a Read tool in the Jshookmcp MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on tls_read_until? +

Register the Jshook MCP server in PolicyLayer and add a rule for tls_read_until: 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 tls_read_until? +

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

Can I rate-limit tls_read_until? +

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

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

tls_read_until 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 →

Across the catalogue

read_input_file on 0gzk → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →