Compare previous and current collected file summaries.
AI agents call collection_diff 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 and analyzes existing data (file summaries) to identify differences. It performs no side effects, does not execute code, does not modify or delete data, and does not affect external systems. It is purely informational and analytical in nature, fitting the 'Read' category for query and comparison operations. The low severity reflects minimal blast radius if misused by an AI agent.
From the tool's definition Tool description states 'Compare previous and current collected file summaries' — a direct comparison operation with no modification, deletion, or execution involved. The verb 'compare' is a read-only analytical operation.
Attacks that exploit this kind of access
Compare previous and current collected file summaries. 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 collection_diff: 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.
collection_diff 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 collection_diff 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 collection_diff. 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.
collection_diff 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 →