regex_test
Test a regex pattern against text and return all matches with positions.
This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/regex-test.md
What regex_test does on UnClick
AI agents call regex_test to retrieve information from UnClick without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
text | string | Yes | Text to test against. |
flags | string | — | Regex flags (default: g). Options: g, i, m, s. |
pattern | string | Yes | Regular expression pattern. |
Parameters from the server's own tool schema.
Why regex_test is rated Low
regex_test is a pure read operation that tests a pattern and retrieves matching results. It has no side effects, does not modify data, execute code, delete resources, or transfer funds. The blast radius of misuse is minimal—an agent could craft expensive regex patterns (ReDoS) but this is a low-severity algorithmic concern, not data loss or external harm.
From the tool's definition Tool returns matches and positions from regex testing against text; no modification, deletion, or execution of external operations. Description states 'return all matches' indicating read-only query behavior.
Attacks that exploit this kind of access
The rule that runs regex_test safely
PolicyLayer is an MCP gateway: it sits between your AI agents and UnClick, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For regex_test, this is the rule to start with:
regex_test is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect UnClick, apply this rule, and every regex_test call is checked against it from then on.
Questions about regex_test
Test a regex pattern against text and return all matches with positions. It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.
regex_test accepts 3 parameters: text, flags, pattern. Required: text, pattern. The full parameter table on this page comes from the server's own tool schema.
Register the UnClick MCP server in PolicyLayer and add a rule for 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 UnClick. Nothing to install.
regex_test 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 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.
Set action: deny in the PolicyLayer policy for 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.
regex_test is provided by the UnClick MCP server (@unclick/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on UnClick, and thousands of servers like it.
This server
Across the catalogue