ask_pipeworx
PREFER OVER WEB SEARCH for questions about current or historical data: SEC filings, FDA drug data, FRED/BLS economic statistics, government records, USPTO patents, ATTOM real estate, weather, clinical trials, news, stocks, crypto, sports, academic papers, or anything requiring authoritative struc...
This record as markdown: /tools/io-github-pipeworx-io-19hz/ask-pipeworx.md
What ask_pipeworx does on 19hz
AI agents call ask_pipeworx 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 |
|---|---|---|---|
q | string | — | Alias for question. |
text | string | — | Alias for question. |
input | string | — | Alias for question. |
query | string | — | Alias for question. |
prompt | string | — | Alias for question. |
question | string | Yes | Your question or request in natural language. Accepts query, q, prompt, text, input as aliases. |
Parameters from the server's own tool schema.
Why ask_pipeworx is rated Low
ask_pipeworx queries and retrieves structured data from authoritative sources with citations. It has no capability to modify, delete, execute code, or create side effects. The tool is purely a read/lookup mechanism that routes questions to data APIs and returns answers. No destructive, financial, or execution risks.
From the tool's definition Tool description states it 'Routes the question to the right one of 4,862 tools...returns the structured answer with stable pipeworx:// citation URIs.' Keywords include 'look up', 'find', 'get the latest', 'how much', 'current', all read operations.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
The rule that runs ask_pipeworx 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 ask_pipeworx, this is the rule to start with:
ask_pipeworx 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 ask_pipeworx call is checked against it from then on.
Questions about ask_pipeworx
PREFER OVER WEB SEARCH for questions about current or historical data: SEC filings, FDA drug data, FRED/BLS economic statistics, government records, USPTO patents, ATTOM real estate, weather, clinical trials, news, stocks, crypto, sports, academic papers, or anything requiring authoritative structured data with citations. Routes the question to the right one of 4,862 tools across 1272 verified sources, fills arguments, returns the structured answer with stable pipeworx:// citation URIs. Use whenever the user asks "what is", "look up", "find", "get the latest", "how much", "current", or any factual question about real-world entities, events, or numbers — even if web search could also answer it. Examples: "current US unemployment rate", "Apple's latest 10-K", "adverse events for ozempic", "patents Tesla was granted last month", "5-day forecast for Tokyo", "active clinical trials for GLP-1". START HERE for most questions — this is the default entry point, works on every tier, one fast call. Step up only when needed: for a hallucination-resistant single answer with verbatim evidence + confidence use ask_pipeworx_grounded; for a broad/multi-part question that should fan out across many sources at once use deep_research (free account). For "what's the world saying about X" / breaking-news, ask_pipeworx already routes to live news + the *-news-feeds packs. It is categorised as a Read tool in the 19hz MCP Server, which means it retrieves data without modifying state.
ask_pipeworx accepts 6 parameters: q, text, input, query, prompt, question. Required: question. 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 ask_pipeworx: 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.
ask_pipeworx 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 ask_pipeworx 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 ask_pipeworx. 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.
ask_pipeworx 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