slug_generate
URL Slug Generator — Transliterate text to ASCII (Unicode NFKD, diacritics stripped) and collapse it into a URL-safe, hyphenated slug.
This record as markdown: /tools/com-wingmanprotocol-agent-gateway/slug-generate.md
What slug_generate does on Gateway
AI agents call slug_generate to retrieve information from Gateway 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 slugify |
lowercase | boolean | — | Lowercase the slug (default true) |
separator | string | — | Separator character (default '-') |
max_length | integer | — | Truncate the slug to at most this many characters |
Parameters from the server's own tool schema.
Why slug_generate is rated Low
This tool performs a pure text transformation — converting input text into a URL slug — with no side effects, no data storage, no deletion, and no external operations. It simply reads input and returns a derived string.
From the tool's definition Transliterate text to ASCII (Unicode NFKD, diacritics stripped) and collapse it into a URL-safe, hyphenated slug
Attacks that exploit this kind of access
The rule that runs slug_generate safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Gateway, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For slug_generate, this is the rule to start with:
slug_generate 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 Gateway, apply this rule, and every slug_generate call is checked against it from then on.
Questions about slug_generate
URL Slug Generator — Transliterate text to ASCII (Unicode NFKD, diacritics stripped) and collapse it into a URL-safe, hyphenated slug. It is categorised as a Read tool in the Gateway MCP Server, which means it retrieves data without modifying state.
slug_generate accepts 4 parameters: text, lowercase, separator, max_length. Required: text. The full parameter table on this page comes from the server's own tool schema.
Register the Gateway MCP server in PolicyLayer and add a rule for slug_generate: 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 Gateway. Nothing to install.
slug_generate 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 slug_generate 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 slug_generate. 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.
slug_generate is provided by the Gateway MCP server (https://wingmanprotocol.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Gateway, and thousands of servers like it.
This server
Across the catalogue