What can I ask Pipeworx? / what is Pipeworx good for? / what can you do? / give me ideas / show me examples / getting started / what data do you have? — the onboarding entry point for an agent that just connected and wants to know what is worth asking. Returns category-bucketed example questions ...
AI agents call suggest_questions to retrieve information from Mcp Powo without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
topic | string | — | Optional focus area: finance | pharma | economics | real-estate | betting | weather | government | science | news. Omit for a cross-category spread. |
Parameters from the server's own tool schema.
suggest_questions is a discovery and documentation tool that retrieves and displays metadata about the Pipeworx system's capabilities. It performs a read-only query of example questions and available tools, with no capacity to modify data, execute code, or trigger external operations.
From the tool's definition Tool provides 'example questions' and 'category-bucketed' reference information about available tools and capabilities. Returns informational content about what can be queried, with no mention of modifying, deleting, or executing operations.
Attacks that exploit this kind of access
What can I ask Pipeworx? / what is Pipeworx good for? / what can you do? / give me ideas / show me examples / getting started / what data do you have? — the onboarding entry point for an agent that just connected and wants to know what is worth asking. Returns category-bucketed example questions (company financials, drugs & clinical trials, economics, real estate, prediction markets, weather, government & patents, science & academia, news) — each with the exact tool + argument shape that answers it, drawn from the live catalog of thousands of tools. Call with no arguments for the full spread, or pass topic (e.g. "finance", "pharma", "betting") to focus. Use this FIRST when you do not yet know what Pipeworx can do for you, or to learn how to call the meta-tools (ask_pipeworx, entity_profile, compare_entities, etc.). It is categorised as a Read tool in the Mcp Powo MCP Server, which means it retrieves data without modifying state.
suggest_questions accepts 1 parameter: topic. The full parameter table on this page comes from the server's own tool schema.
Register the Mcp Powo MCP server in PolicyLayer and add a rule for suggest_questions: 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 Powo. Nothing to install.
suggest_questions 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 suggest_questions 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 suggest_questions. 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.
suggest_questions is provided by the Mcp Powo MCP server (pipeworx-io/mcp-powo). 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 →