events
List upcoming electronic/dance music events for a 19hz region. Optionally filter by keyword (matches title, venue, genre, or artist) and a date window. Returns normalized events sorted by date.
This record as markdown: /tools/io-github-pipeworx-io-19hz/events.md
What events does on 19hz
AI agents call events to retrieve information from 19hz without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
to | string | — | Only events on/before this date (YYYY-MM-DD). |
from | string | — | Only events on/after this date (YYYY-MM-DD). |
limit | number | — | Max events to return (1-200, default 50). |
query | string | — | Optional keyword filter, e.g. "techno", a venue name, or an artist. |
region | string | Yes | Region slug, e.g. "bayarea", "losangeles", "texas". Use the regions tool to list all. |
Parameters from the server's own tool schema.
Why events is rated Low
Even though events only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
Attacks that exploit this kind of access
The rule that runs events safely
PolicyLayer is an MCP gateway: it sits between your AI agents and 19hz, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For events, this is the rule to start with:
events is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect 19hz, apply this rule, and every events call is checked against it from then on.
Questions about events
List upcoming electronic/dance music events for a 19hz region. Optionally filter by keyword (matches title, venue, genre, or artist) and a date window. Returns normalized events sorted by date. It is categorised as a Read tool in the 19hz MCP Server, which means it retrieves data without modifying state.
events accepts 5 parameters: to, from, limit, query, region. Required: region. The full parameter table on this page comes from the server's own tool schema.
Register the 19hz MCP server in PolicyLayer and add a rule for 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 19hz. Nothing to install.
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 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 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.
events is provided by the 19hz MCP server (https://gateway.pipeworx.io/19hz/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on 19hz, and thousands of servers like it.
This server
Across the catalogue