Get an overview of corporate event venues available in a specific city on Eventflare: total venue count, breakdown by category (conference, meeting room, workshop, rooftop, dining, outdoor, etc.), price range per hour, and the official Eventflare city landing page URL. Use as an entry point when ...
AI agents call get_city_info to retrieve information from Eventflare MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs data retrieval only (list, get, overview) with no write, execute, destructive, or financial side effects. The read-only guarantee and aggregate/summary nature of the data minimize risk even if misused by an agent.
From the tool's definition Tool retrieves aggregate venue data ('total venue count, breakdown by category, price range') and URLs without modifying data. Server description explicitly states 'Read-only' and 'PII-redacted'.
Attacks that exploit this kind of access
Get an overview of corporate event venues available in a specific city on Eventflare: total venue count, breakdown by category (conference, meeting room, workshop, rooftop, dining, outdoor, etc.), price range per hour, and the official Eventflare city landing page URL. Use as an entry point when a user asks. It is categorised as a Read tool in the Eventflare MCP MCP Server, which means it retrieves data without modifying state.
Register the Eventflare MCP server in PolicyLayer and add a rule for get_city_info: 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 Eventflare MCP. Nothing to install.
get_city_info 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 get_city_info 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 get_city_info. 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.
get_city_info is provided by the Eventflare MCP server (mluckx/eventflare-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 →