AI agents call yelp_search_events to retrieve information from UnClick without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
api_key | string | — | |
location | string | — | |
categories | string | — | |
start_date | number | — |
Parameters from the server's own tool schema.
This tool searches public event data on Yelp without creating, modifying, deleting, or executing operations. It is a straightforward read operation that retrieves information. The blast radius of misuse is minimal—an agent could retrieve unwanted event data but cannot cause harm, financial loss, or data destruction.
From the tool's definition Tool name 'yelp_search_events' and description 'Search for events on Yelp' indicate a query/retrieval operation with no side effects.
Risk signalsHandles credentials or secrets (api_key)
Attacks that exploit this kind of access
Search for events on Yelp. It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.
yelp_search_events accepts 4 parameters: api_key, location, categories, start_date. 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 yelp_search_events: 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.
yelp_search_events 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 yelp_search_events 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 yelp_search_events. 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.
yelp_search_events 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.
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 →