unclick_regex_test
Test a regex pattern against text and get all matches with groups.
This record as markdown: /tools/creativelead-unclick/unclick-regex-test.md
What unclick_regex_test does on UnClick
AI agents call unclick_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 |
|---|---|---|---|
flags | string | — | Flags like 'gi' |
input | string | — | |
pattern | string | — | Regex pattern (no surrounding slashes) |
Parameters from the server's own tool schema.
Why unclick_regex_test is rated Low
The tool performs regex testing and match retrieval, which is fundamentally a read operation that analyzes input text and returns matching results. There are no side effects, data modifications, external command execution, or destructive actions.
From the tool's definition Tool description states 'Test a regex pattern against text and get all matches with groups' - this is a pattern matching and analysis operation that retrieves/queries results from provided input without modifying, deleting, or executing external operations.
Attacks that exploit this kind of access
The rule that runs unclick_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 unclick_regex_test, this is the rule to start with:
unclick_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 unclick_regex_test call is checked against it from then on.
Questions about unclick_regex_test
Test a regex pattern against text and get all matches with groups. It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.
unclick_regex_test accepts 3 parameters: flags, input, 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 unclick_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.
unclick_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 unclick_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 unclick_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.
unclick_regex_test is provided by the UnClick MCP server (creativelead/unclick). 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