List available stealth presets.
AI agents call list_stealth_presets 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 performs a simple enumeration or query operation ('list') to return information about stealth presets. It has no side effects, does not execute code, does not modify data, and does not interact with external systems beyond retrieving stored configuration. The low severity reflects minimal blast radius if misused—an AI agent listing stealth presets cannot cause harm through this read operation alone.
From the tool's definition Tool name 'list_stealth_presets' and description 'List available stealth presets' indicate a read-only operation that retrieves information about available presets without modifying or executing anything.
Attacks that exploit this kind of access
List available stealth presets. 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 list_stealth_presets: 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.
list_stealth_presets 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 list_stealth_presets 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 list_stealth_presets. 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.
list_stealth_presets 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 →