dev.regex-test

SERVERMcp SOURCE@2sio/mcp

High RISK CLASS

Category Execute

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-2s-io-mcp/dev.regex-test.md

WHAT IT DOES

What dev.regex-test does on Mcp

AI agents invoke dev.regex-test to trigger actions in Mcp. 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.

RISK

Why dev.regex-test is rated High

The tool runs JavaScript regex evaluation (code execution) on user-supplied pattern and input. While it has no side effects or upstream calls, it executes computation based on arbitrary user-supplied patterns, placing it in the Execute category.

From the tool's definition "Test a JavaScript regular expression against input text" and "Pure compute, no upstream" — executes regex pattern matching code against provided input

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs dev.regex-test safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Mcp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For dev.regex-test, this is the rule to start with:

dev.regex-test Rate-limited

dev.regex-test 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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "dev.regex-test": {
      "limits": [
        {
          "counter": "dev.regex-test_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Mcp, apply this rule, and every dev.regex-test call is checked against it from then on.

FAQ

Questions about dev.regex-test

What does the dev.regex-test tool do? +

Test a JavaScript regular expression against input text. POST { pattern, flags?, input }. Returns each match with its index, numbered capture groups, and named groups (up to 1000 matches with the g flag). Pure compute, no upstream. It is categorised as a Execute tool in the Mcp MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on dev.regex-test? +

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

What risk level is dev.regex-test? +

dev.regex-test is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit dev.regex-test? +

Yes. Add a rate_limit block to the dev.regex-test 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 dev.regex-test completely? +

Set action: deny in the PolicyLayer policy for dev.regex-test. 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 dev.regex-test? +

dev.regex-test is provided by the MCP server (@2sio/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on , and thousands of servers like it.

This server

All 572 tools → High-risk tools on this server →

Across the catalogue

execute_test_case on Percepta MCP Server → All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →