This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/urban-define.md
What urban_define does on UnClick
AI agents call urban_define 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 |
|---|---|---|---|
term | string | Yes | Slang term to define |
Parameters from the server's own tool schema.
Why urban_define is rated Low
This tool performs a read-only lookup of publicly available slang definitions. It retrieves information without creating, modifying, deleting, or executing any operations. The only potential concern would be if the definitions themselves contain harmful content, but the tool's function is purely informational retrieval, making it a Read category with low severity.
From the tool's definition Tool name 'urban_define' and description 'Look up slang definitions on Urban Dictionary' indicate a query/retrieval operation with no data modification or side effects.
Attacks that exploit this kind of access
The rule that runs urban_define 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 urban_define, this is the rule to start with:
urban_define 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 urban_define call is checked against it from then on.
Questions about urban_define
Look up slang definitions on Urban Dictionary. It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.
urban_define accepts 1 parameter: term. Required: term. 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 urban_define: 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.
urban_define 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 urban_define 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 urban_define. 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.
urban_define 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