Search events inside one Bushdrum city. Args: city: Required Bushdrum city slug such as zurich or berlin. limit: Number of results to return. Defaults to 10 and is capped at 20. q: Plain search query for titles, venue names, and summaries. category: One or mor...
High parameter count (18 properties)
Part of the Bushdrum Events MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.
AI agents call search_events to retrieve information from Bushdrum Events without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.
Even though search_events only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.
Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.
tools:
search_events:
rules:
- action: allowSee the full Bushdrum Events policy for all 2 tools.
Agents calling read-class tools like search_events have been implicated in these attack patterns. Read the full case and prevention policy for each:
Other tools in the Read risk category across the catalogue. The same policy patterns (rate-limit, allow) apply to each.
Search events inside one Bushdrum city. Args: city: Required Bushdrum city slug such as zurich or berlin. limit: Number of results to return. Defaults to 10 and is capped at 20. q: Plain search query for titles, venue names, and summaries. category: One or more event categories. subcategory: One subcategory value. vibe: One or more vibe filters. audience: One or more audience filters. neighborhood: Neighborhood filter scoped to the chosen city. date_from: Start date in YYYY-MM-DD format. date_to: End date in YYYY-MM-DD format. is_free: Only return free events when true. price_max: Maximum ticket price. indoor_outdoor: indoor, outdoor, or both. event_language: Event language code such as de or en. tags: One or more tag filters. time_from: Start time filter in HH:MM format. time_to: End time filter in HH:MM format. age_max: Maximum age suitability filter. . It is categorised as a Read tool in the Bushdrum Events MCP Server, which means it retrieves data without modifying state.
Add a rule in your Intercept YAML policy under the tools section for search_events. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Bushdrum Events MCP server.
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 search_events rule in your Intercept 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 Intercept policy for 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.
search_events is provided by the Bushdrum Events MCP server (justus/bushdrum-events). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Open source. One binary. Zero dependencies.
npx -y @policylayer/intercept