Search for art events that are visitable during a date range or on a specific date. Returns events whose date ranges intersect with the search range. Args: start_date: Start date in YYYY-MM-DD format (optional if specific_date is provided) ...
Single-target operation
Part of the Art Events MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.
AI agents call search_events_by_date_range to retrieve information from Art 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_by_date_range 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_by_date_range:
rules:
- action: allowSee the full Art Events policy for all 3 tools.
Agents calling read-class tools like search_events_by_date_range 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 for art events that are visitable during a date range or on a specific date. Returns events whose date ranges intersect with the search range. Args: start_date: Start date in YYYY-MM-DD format (optional if specific_date is provided) end_date: End date in YYYY-MM-DD format (optional if specific_date is provided) specific_date: Specific date in YYYY-MM-DD format (alternative to date range) Returns: JSON string containing events that are visitable during the specified date range . It is categorised as a Read tool in the Art 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_by_date_range. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Art Events MCP server.
search_events_by_date_range 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_by_date_range 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_by_date_range. 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_by_date_range is provided by the Art Events MCP server (onurgu/art-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