ask_pipeworx_beta
Beta version of ask_pipeworx: identical universal router (same 5,114 tools, same arguments, same response shape) with candidate routing improvements enabled live — currently source-preference ranking: when your question names a source, it wins ("using OpenAlex, not PubMed" boosts OpenAlex and dem...
This record as markdown: /tools/io-github-pipeworx-io-linear/ask-pipeworx-beta.md
What ask_pipeworx_beta does on Linear
AI agents call ask_pipeworx_beta to retrieve information from Linear 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_beta is rated Low
Even though ask_pipeworx_beta only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
Attacks that exploit this kind of access
The rule that runs ask_pipeworx_beta safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Linear, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For ask_pipeworx_beta, this is the rule to start with:
ask_pipeworx_beta 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 Linear, apply this rule, and every ask_pipeworx_beta call is checked against it from then on.
Questions about ask_pipeworx_beta
Beta version of ask_pipeworx: identical universal router (same 5,114 tools, same arguments, same response shape) with candidate routing improvements enabled live — currently source-preference ranking: when your question names a source, it wins ("using OpenAlex, not PubMed" boosts OpenAlex and demotes PubMed). Use it exactly like ask_pipeworx when you want the newest routing; results are compared against the stable router to decide what merges. Falls back to nothing — this IS a full working router, just the experimental edge. It is categorised as a Read tool in the Linear MCP Server, which means it retrieves data without modifying state.
ask_pipeworx_beta 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 Linear MCP server in PolicyLayer and add a rule for ask_pipeworx_beta: 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 Linear. Nothing to install.
ask_pipeworx_beta 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_beta 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_beta. 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_beta is provided by the Linear MCP server (https://gateway.pipeworx.io/linear/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Linear, and thousands of servers like it.
This server
Across the catalogue