regex_escape
Escape special regex characters in a string for literal matching.
This record as markdown: /tools/io-github-scotia1973-bot-api-hub/regex-escape.md
What regex_escape does on GadgetHumans API Hub
AI agents call regex_escape to retrieve information from GadgetHumans API Hub without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why regex_escape is rated Low
This tool processes a string and returns an escaped version suitable for literal regex matching. It is a pure text transformation with no side effects, no data storage, no external calls, and no destructive or financial implications. It reads/transforms input and returns output, making it a Read-category tool with low severity.
From the tool's definition Escape special regex characters in a string for literal matching
Attacks that exploit this kind of access
The rule that runs regex_escape safely
PolicyLayer is an MCP gateway: it sits between your AI agents and GadgetHumans API Hub, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For regex_escape, this is the rule to start with:
regex_escape 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 GadgetHumans API Hub, apply this rule, and every regex_escape call is checked against it from then on.
Questions about regex_escape
Escape special regex characters in a string for literal matching. It is categorised as a Read tool in the GadgetHumans API Hub MCP Server, which means it retrieves data without modifying state.
Register the GadgetHumans API Hub MCP server in PolicyLayer and add a rule for regex_escape: 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 GadgetHumans API Hub. Nothing to install.
regex_escape 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_escape 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_escape. 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_escape is provided by the GadgetHumans API Hub MCP server (pypi:gadgethumans-api-hub-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on GadgetHumans API Hub, and thousands of servers like it.
This server
Across the catalogue