filter_events_by_date
AI agents call filter_events_by_date to retrieve information from MCP Travel Planner without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves or filters event data based on date criteria. The 'filter_' verb pattern across the entire server consistently indicates retrieval operations without mutations. No deletion, execution, or financial operations are implied. Lower confidence (0.85 not higher) due to empty description, but the sibling context provides strong evidence of Read category intent.
From the tool's definition Tool name 'filter_events_by_date' indicates querying/filtering events by a date parameter, consistent with sibling tools that all use 'filter_' prefix (filter_events_by_type, filter_events_by_venue, filter_flights_by_airline, etc.) which are Read operations.
Attacks that exploit this kind of access
filter_events_by_date. It is categorised as a Read tool in the MCP Travel Planner MCP Server, which means it retrieves data without modifying state.
Register the MCP Travel Planner MCP server in PolicyLayer and add a rule for filter_events_by_date: 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 MCP Travel Planner. Nothing to install.
filter_events_by_date 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 filter_events_by_date 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 filter_events_by_date. 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.
filter_events_by_date is provided by the MCP Travel Planner MCP server (leonavevor/mcp_travelassistant). 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 →