New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

re_js

JavaScript bundle: endpoints, suspect secrets (redacted), obfuscation signals; optional webcrack.

SERVERRekit SOURCEAmz34/rekit
Low RISK CLASS
Category Other
Parameters 00 required
Recommended Rate-limitedsee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/rekit/re-js.md

What re_js does on Rekit

AI agents call re_js as a supporting operation in Rekit workflows.

Why re_js is rated Low

Without any rule in front of it, every call an agent makes to re_js happens silently: no trail, no cap, no way to know it misbehaved until something breaks downstream.

Questions about re_js

What does the re_js tool do? +

JavaScript bundle: endpoints, suspect secrets (redacted), obfuscation signals; optional webcrack. It is categorised as a Other tool in the Rekit MCP Server, which means it performs auxiliary operations.

How do I enforce a policy on re_js? +

Register the Rekit MCP server in PolicyLayer and add a rule for re_js: 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 Rekit. Nothing to install.

What risk level is re_js? +

re_js is a Other tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit re_js? +

Yes. Add a rate_limit block to the re_js 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.

How do I block re_js completely? +

Set action: deny in the PolicyLayer policy for re_js. 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.

What MCP server provides re_js? +

re_js is provided by the Rekit MCP server (Amz34/rekit). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

More on Rekit, and thousands of servers like it.

Across the catalogue

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Rekit's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.