coverage_report
Report which tools have been called in the current runtime and which known tools remain uncalled.
This record as markdown: /tools/io-github-vmoranv-jshookmcp/coverage-report.md
What coverage_report does on Jshookmcp
AI agents call coverage_report 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.
Why coverage_report is rated Low
This tool queries and reports on the state of tool invocations within the current runtime session. It retrieves information about which tools have been called and which have not been called, performing read-only analysis with no side effects, data modification, code execution, or destructive operations. The blast radius is minimal—misuse would only result in information disclosure about tool usage patterns.
From the tool's definition Tool name 'coverage_report' and description 'Report which tools have been called in the current runtime and which known tools remain uncalled' indicate retrieval and analysis of execution data with no modifications, deletions, or external operations.
Attacks that exploit this kind of access
The rule that runs coverage_report 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 coverage_report, this is the rule to start with:
coverage_report is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Jshookmcp, apply this rule, and every coverage_report call is checked against it from then on.
Questions about coverage_report
Report which tools have been called in the current runtime and which known tools remain uncalled. It is categorised as a Read tool in the Jshookmcp MCP Server, which means it retrieves data without modifying state.
Register the Jshook MCP server in PolicyLayer and add a rule for coverage_report: 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.
coverage_report is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the coverage_report 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.
Set action: deny in the PolicyLayer policy for coverage_report. 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.
coverage_report 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.
More on Jshook, and thousands of servers like it.
This server
Across the catalogue