page_coverage_stop

Stop coverage collection and return per-script JS+CSS coverage results. Includes total bytes, used bytes, and coverage percentage per URL.

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/page-coverage-stop.md

WHAT IT DOES

What page_coverage_stop does on Jshookmcp

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

Stops coverage and returns collected data; no destructive or modifying side effects.

From the tool's definition Stop coverage collection and return per-script JS+CSS coverage results

Attacks that exploit this kind of access

RECOMMENDED RULE

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

page_coverage_stop Allowed

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

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

FAQ

Questions about page_coverage_stop

What does the page_coverage_stop tool do? +

Stop coverage collection and return per-script JS+CSS coverage results. Includes total bytes, used bytes, and coverage percentage per URL. 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 page_coverage_stop? +

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

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

Can I rate-limit page_coverage_stop? +

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

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

page_coverage_stop 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

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