tls_keylog_enable

Enable SSLKEYLOGFILE output for TLS library clients.

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/tls-keylog-enable.md

WHAT IT DOES

What tls_keylog_enable does on Jshookmcp

AI agents invoke tls_keylog_enable 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 tls_keylog_enable is rated High

Enabling TLS key logging intercepts encrypted traffic, enabling decryption of secure communications.

From the tool's definition Enable SSLKEYLOGFILE output for TLS library clients

Attacks that exploit this kind of access

RECOMMENDED RULE

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

tls_keylog_enable Rate-limited

tls_keylog_enable 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": {
    "tls_keylog_enable": {
      "limits": [
        {
          "counter": "tls_keylog_enable_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 tls_keylog_enable call is checked against it from then on.

FAQ

Questions about tls_keylog_enable

What does the tls_keylog_enable tool do? +

Enable SSLKEYLOGFILE output for TLS library clients. 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 tls_keylog_enable? +

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

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

Can I rate-limit tls_keylog_enable? +

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

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

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