tls_cert_pin_bypass

Return a certificate pinning bypass strategy for the selected platform.

SERVERJshookmcp SOURCE@jshookmcp/jshook

Medium RISK CLASS

Category Write

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-cert-pin-bypass.md

WHAT IT DOES

What tls_cert_pin_bypass does on Jshookmcp

AI agents use tls_cert_pin_bypass to create or update resources in Jshookmcp, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Jshookmcp environment.

RISK

Why tls_cert_pin_bypass is rated Medium

An AI agent can call tls_cert_pin_bypass faster than any human can review: one bad instruction and it creates or modifies resources in Jshookmcp by the hundred, each call as confident as the last.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

tls_cert_pin_bypass Rate-limited

tls_cert_pin_bypass stays usable, but capped: an agent stuck in a loop can't make hundreds of changes 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_cert_pin_bypass": {
      "limits": [
        {
          "counter": "tls_cert_pin_bypass_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

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_cert_pin_bypass call is checked against it from then on.

FAQ

Questions about tls_cert_pin_bypass

What does the tls_cert_pin_bypass tool do? +

Return a certificate pinning bypass strategy for the selected platform. It is categorised as a Write tool in the Jshookmcp MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on tls_cert_pin_bypass? +

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

tls_cert_pin_bypass is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit tls_cert_pin_bypass? +

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

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

tls_cert_pin_bypass 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

The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →