network_bot_detect_analyze

Analyze captured requests for bot-detection signals. Optionally supply a JA3/JA4 TLS fingerprint (from network_tls_fingerprint parse_client_hello) plus user-defined knownBad hash lists; matching hashes raise the bot score. Ships NO hardcoded feature library — the caller decides which hashes are b...

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/network-bot-detect-analyze.md

WHAT IT DOES

What network_bot_detect_analyze does on Jshookmcp

AI agents call network_bot_detect_analyze 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 network_bot_detect_analyze is rated Low

Tool analyzes network data and computes bot scores without modifying systems or executing code.

From the tool's definition Analyze captured requests for bot-detection signals; no modification or execution capability.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

network_bot_detect_analyze Allowed

network_bot_detect_analyze 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": {
    "network_bot_detect_analyze": {}
  }
}

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

FAQ

Questions about network_bot_detect_analyze

What does the network_bot_detect_analyze tool do? +

How do I enforce a policy on network_bot_detect_analyze? +

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

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

Can I rate-limit network_bot_detect_analyze? +

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

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

network_bot_detect_analyze 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

detect_slop on Slop Cop → The MCP Attack Database →

Guides

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