List packaged parameter workflows that can guide reverse-engineering and rebuild steps.
AI agents call list_parameter_workflows 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 enumeration of existing workflow definitions. It queries and returns information about available parameter workflows, which is a read operation with no side effects, no code execution, no data modification, and no destructive action. The severity is low because listing workflows poses minimal risk—it only exposes metadata about available options without executing them or altering system state.
From the tool's definition Tool name 'list_parameter_workflows' and description 'List packaged parameter workflows' indicate a read-only operation that retrieves and displays available workflows without modifying data or triggering actions.
Attacks that exploit this kind of access
List packaged parameter workflows that can guide reverse-engineering and rebuild steps. 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_parameter_workflows: 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_parameter_workflows 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_parameter_workflows 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_parameter_workflows. 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_parameter_workflows 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 →