Test regex patterns against text
AI agents invoke test-regex to trigger actions in Underground Cultural District MCP Server. 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.
Executing regex patterns against arbitrary input constitutes running a computation/pattern-matching operation. While typically low-risk, regex execution can be exploited via ReDoS (Regular Expression Denial of Service) attacks with crafted patterns causing catastrophic backtracking, making it an Execute-category tool with medium severity.
From the tool's definition Test regex patterns against text
Attacks that exploit this kind of access
Test regex patterns against text. It is categorised as a Execute tool in the Underground Cultural District MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Underground Cultural District MCP Server MCP server in PolicyLayer and add a rule for test-regex: 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 Underground Cultural District MCP Server. Nothing to install.
test-regex 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 test-regex 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 test-regex. 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.
test-regex is provided by the Underground Cultural District MCP Server MCP server (lisamaraventano-spine/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →