Fetch a single PredictHQ event by its id, returning its title, category, rank, predicted attendance, dates, and location. Example: get_event({ id: "abcDEF123" }).
AI agents call get_event 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 |
|---|---|---|---|
id | string | Yes | The PredictHQ event id, e.g. "abcDEF123". |
_apiKey | string | — | Optional — your own PredictHQ access token for your own quota; omit to use the shared Pipeworx platform key. |
Parameters from the server's own tool schema.
This tool queries an external API to retrieve event information by ID and returns structured data. No data is created, modified, deleted, or executed. The tool is read-only and has minimal blast radius if misused—at worst it could expose public event data or be used for reconnaissance, but carries no destructive, financial, or execution risks.
From the tool's definition 'Fetch a single PredictHQ event by its id, returning its title, category, rank, predicted attendance, dates, and location' — describes retrieval of event data with no modification, deletion, or side effects.
Attacks that exploit this kind of access
Fetch a single PredictHQ event by its id, returning its title, category, rank, predicted attendance, dates, and location. Example: get_event({ id: "abcDEF123" }). It is categorised as a Read tool in the Mcp Predicthq MCP Server, which means it retrieves data without modifying state.
get_event accepts 2 parameters: id, _apiKey. Required: id. 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 get_event: 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.
get_event 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_event 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_event. 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_event 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 →