api_probe_batch

Batch-probe API endpoints in browser context with auto token injection and HTML skip.

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/api-probe-batch.md

WHAT IT DOES

What api_probe_batch does on Jshookmcp

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

Executes multiple API requests in browser context with automatic authentication injection.

From the tool's definition Batch-probe API endpoints in browser context with auto token injection

Attacks that exploit this kind of access

RECOMMENDED RULE

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

api_probe_batch Rate-limited

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

FAQ

Questions about api_probe_batch

What does the api_probe_batch tool do? +

Batch-probe API endpoints in browser context with auto token injection and HTML skip. 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 api_probe_batch? +

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

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

Can I rate-limit api_probe_batch? +

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

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

api_probe_batch 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

qt_batch on Qt → All high-risk MCP tools → The MCP Attack Database →

Guides

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