api_request
Make an HTTP request from the browser context. Supports custom method, headers, body, and automatic token injection. The request is executed inside the browser page using fetch(), so it shares cookies and origin with the page. Use tokenName or the active token for automatic auth header injection.
This record as markdown: /tools/1600822305-js-reverse-mcp/api-request.md
What api_request does on Js Reverse
AI agents invoke api_request to trigger actions in Js Reverse. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
Why api_request is rated High
This tool executes arbitrary HTTP requests (any method including POST, PUT, DELETE, etc.) from within the browser context, sharing cookies and origin. It can trigger external operations, modify remote data, or even destructive actions depending on the request made. The automatic token injection adds an authentication escalation risk.
From the tool's definition Make an HTTP request from the browser context... executed inside the browser page using fetch()... Supports custom method, headers, body, and automatic token injection
Attacks that exploit this kind of access
The rule that runs api_request safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Js Reverse, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For api_request, this is the rule to start with:
api_request stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Js Reverse, apply this rule, and every api_request call is checked against it from then on.
Questions about api_request
Make an HTTP request from the browser context. Supports custom method, headers, body, and automatic token injection. The request is executed inside the browser page using fetch(), so it shares cookies and origin with the page. Use tokenName or the active token for automatic auth header injection. It is categorised as a Execute tool in the Js Reverse MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Js Reverse MCP server in PolicyLayer and add a rule for api_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. Nothing to install.
api_request is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the api_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 api_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.
api_request is provided by the Js Reverse MCP server (1600822305/js-reverse-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Js Reverse, and thousands of servers like it.
Across the catalogue