edinburgh_festival_events
AI agents call edinburgh_festival_events to retrieve information from Edinburgh Festivals MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves event information from the Edinburgh Festivals API with no indication of side effects, data modification, deletion, or external operations. The ability to query historical data further confirms read-only access. The low severity reflects minimal risk even if misused by an AI agent—retrieving public festival event information poses no security, financial, or destructive risk.
From the tool's definition Tool name 'edinburgh_festival_events' combined with server context describing 'querying the Edinburgh Festivals API to retrieve information about events' indicates a data retrieval operation.
Attacks that exploit this kind of access
edinburgh_festival_events. It is categorised as a Read tool in the Edinburgh Festivals MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Edinburgh Festivals MCP Server MCP server in PolicyLayer and add a rule for edinburgh_festival_events: 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 Edinburgh Festivals MCP Server. Nothing to install.
edinburgh_festival_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 edinburgh_festival_events 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 edinburgh_festival_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.
edinburgh_festival_events is provided by the Edinburgh Festivals MCP Server MCP server (richarda23/edfest-mcp). 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 →