Create a reverse task directly from one captured network request.
AI agents use create_reverse_task_from_request to create or update resources in JS Reverse MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your JS Reverse MCP environment.
The tool creates a new task object/record based on a captured network request. This is a Write operation (creating data). It does not execute code, delete data, or involve finances. Severity is medium because in a reverse engineering context, creating tasks could initiate subsequent analysis workflows, but the tool itself is a creation/write action.
From the tool's definition Create a reverse task directly from one captured network request
Attacks that exploit this kind of access
Create a reverse task directly from one captured network request. It is categorised as a Write tool in the JS Reverse MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the JS Reverse MCP server in PolicyLayer and add a rule for create_reverse_task_from_request: 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.
create_reverse_task_from_request is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the create_reverse_task_from_request 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 create_reverse_task_from_request. 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.
create_reverse_task_from_request 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.
create_reverse_task_from_request is one line of JS Reverse's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →