search_events

Search the PredictHQ Events API for real-world events (concerts, sports, conferences, festivals, public holidays, severe weather, etc.) used for demand forecasting. Filter by free-text query, category, country, and an active-date window; results are ranked by predicted impact. Returns each event ...

Server Mcp Predicthq pipeworx-io/mcp-predicthq
Category Read
Risk class Low
Parameters 70 required

What search_events does on Mcp Predicthq

AI agents call search_events to retrieve information from Mcp Predicthq without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

ParameterTypeRequiredDescription
end string Only include events active on or before this date (YYYY-MM-DD), e.g. "2026-06-30".
limit number Max events to return (default 15, max 50).
query string Free-text search across event titles/descriptions, e.g. "marathon".
start string Only include events active on or after this date (YYYY-MM-DD), e.g. "2026-06-01".
_apiKey string Optional — your own PredictHQ access token for your own quota; omit to use the shared Pipeworx platform key.
country string 2-letter ISO country code, e.g. "US", "GB", "AU".
category string Comma-separated event categories. One or more of: concerts, sports, conferences, expos, festivals, performing-arts, community, public-holidays, observances, pol

Parameters from the server's own tool schema.

Why search_events needs a policy

This tool performs read-only queries against a public events database. It retrieves structured event information for forecasting purposes with no side effects, data modifications, or external operations. The search parameters are constrained (category, country, date windows) and results are informational only. Misuse by an AI agent would be limited to information gathering without irreversible consequences.

From the tool's definition Tool searches and retrieves event data from PredictHQ Events API with filters (query, category, country, date range). Returns event information including rank, attendance, dates, location. No modification, deletion, or execution capabilities described.

Risk signalsAccepts freeform code/query input (query)

Questions about search_events

What does the search_events tool do? +

Search the PredictHQ Events API for real-world events (concerts, sports, conferences, festivals, public holidays, severe weather, etc.) used for demand forecasting. Filter by free-text query, category, country, and an active-date window; results are ranked by predicted impact. Returns each event with its rank, predicted attendance, dates, and location. Example: search_events({ query: "taylor swift", country: "US", category: "concerts", start: "2026-06-01", end: "2026-12-31" }). It is categorised as a Read tool in the Mcp Predicthq MCP Server, which means it retrieves data without modifying state.

What parameters does search_events accept? +

search_events accepts 7 parameters: end, limit, query, start, _apiKey, country, category. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on search_events? +

Register the Mcp Predicthq MCP server in PolicyLayer and add a rule for search_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 Mcp Predicthq. Nothing to install.

What risk level is search_events? +

search_events is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit search_events? +

Yes. Add a rate_limit block to the search_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.

How do I block search_events completely? +

Set action: deny in the PolicyLayer policy for search_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.

What MCP server provides search_events? +

search_events is provided by the Mcp Predicthq MCP server (pipeworx-io/mcp-predicthq). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// LOOK UP ANOTHER 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 →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.