Find PredictHQ events within a radius of a geographic point (latitude/longitude). Useful for "what is happening near this venue/store/airport" demand-forecasting queries. Filter by category and active-date window; results are ranked by predicted impact. Example: nearby_events({ latitude: 40.7128,...
AI agents call nearby_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.
| Parameter | Type | Required | Description |
|---|---|---|---|
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). |
start | string | — | Only include events active on or after this date (YYYY-MM-DD), e.g. "2026-06-01". |
radius | string | — | Search radius with unit, e.g. "10km", "5mi" (default "10km"). |
_apiKey | string | — | Optional — your own PredictHQ access token for your own quota; omit to use the shared Pipeworx platform key. |
category | string | — | Comma-separated event categories. One or more of: concerts, sports, conferences, expos, festivals, performing-arts, community, public-holidays, observances, pol |
latitude | number | Yes | Center latitude in decimal degrees, e.g. 40.7128. |
longitude | number | Yes | Center longitude in decimal degrees, e.g. -74.006. |
Parameters from the server's own tool schema.
This is a straightforward data retrieval operation against the PredictHQ Events API. It accepts query parameters (latitude, longitude, radius, category, date filters) and returns ranked results. There are no side effects, irreversible actions, code execution, or financial implications.
From the tool's definition Tool description explicitly states it 'Find[s] PredictHQ events' and 'query[ies]' data with filtering and ranking. No mutations, deletions, code execution, or financial transactions are mentioned or implied.
Attacks that exploit this kind of access
Find PredictHQ events within a radius of a geographic point (latitude/longitude). Useful for "what is happening near this venue/store/airport" demand-forecasting queries. Filter by category and active-date window; results are ranked by predicted impact. Example: nearby_events({ latitude: 40.7128, longitude: -74.006, radius: "10km", category: "concerts,sports" }). It is categorised as a Read tool in the Mcp Predicthq MCP Server, which means it retrieves data without modifying state.
nearby_events accepts 8 parameters: end, limit, start, radius, _apiKey, category, latitude, longitude. Required: latitude, longitude. The full parameter table on this page comes from the server's own tool schema.
Register the Mcp Predicthq MCP server in PolicyLayer and add a rule for nearby_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.
nearby_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 nearby_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 nearby_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.
nearby_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.
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 →