Filter events from a search by venue names.
AI agents call filter_events_by_venue 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 queries event data based on venue filter criteria. It performs no writes, deletions, code execution, or financial operations. The operation is read-only and poses minimal security risk, consistent with other similar filtering tools on this travel planning server (filter_events_by_date, filter_events_by_type, etc.).
From the tool's definition Tool name 'filter_events_by_venue' and description 'Filter events from a search by venue names' indicate a retrieval/query operation that filters existing event data without modification or side effects.
Attacks that exploit this kind of access
Filter events from a search by venue names. 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_venue: 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_venue 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_venue 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_venue. 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_venue 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 →