Get captured data for one hook or all hooks. Supports raw view and summary view for noise reduction.
AI agents call get_hook_data to retrieve information from JS Reverse MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves previously captured hook data. While the broader server context involves code injection and browser debugging (which have Execute characteristics), this specific tool merely queries and returns captured data without executing new code, modifying state, or triggering side effects.
From the tool's definition Tool description states 'Get captured data for one hook or all hooks' — this is a retrieval operation with no modification of state. The name 'get_hook_data' and the use of 'get' confirm a read-only function.
Attacks that exploit this kind of access
Get captured data for one hook or all hooks. Supports raw view and summary view for noise reduction. It is categorised as a Read tool in the JS Reverse MCP MCP Server, which means it retrieves data without modifying state.
Register the JS Reverse MCP server in PolicyLayer and add a rule for get_hook_data: 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 JS Reverse MCP. Nothing to install.
get_hook_data 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 get_hook_data 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 get_hook_data. 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.
get_hook_data is provided by the JS Reverse MCP server (noone-hub/jsreverser-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →