pipeworx_trending
What other AI agents are calling on Pipeworx right now. Returns the top tools, top packs, and total call volume over a recent window (24h, 7d, or 30d). Useful for: (1) discovering what data sources are hot for current events, (2) confirming a popular tool is the canonical choice before asking you...
This record as markdown: /tools/io-github-pipeworx-io-linear/pipeworx-trending.md
What pipeworx_trending does on Linear
AI agents call pipeworx_trending 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 |
|---|---|---|---|
window | string | — | 24h (default) | 7d | 30d. Shorter windows surface what's hot right now; longer windows show steady-state demand. |
Parameters from the server's own tool schema.
Why pipeworx_trending is rated Low
This tool retrieves and queries aggregated, anonymized usage statistics from a monitoring system. It has no side effects, does not modify data, and does not execute operations. The read-only nature and explicit exclusion of PII make this a straightforward Read category tool with low severity.
From the tool's definition Tool returns aggregated analytics data: 'top tools, top packs, and total call volume' with 'no PII, just (pack, tool, count)'. Explicitly described as providing read-only trend information cached from analytics engine.
Attacks that exploit this kind of access
The rule that runs pipeworx_trending 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 pipeworx_trending, this is the rule to start with:
pipeworx_trending 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 pipeworx_trending call is checked against it from then on.
Questions about pipeworx_trending
What other AI agents are calling on Pipeworx right now. Returns the top tools, top packs, and total call volume over a recent window (24h, 7d, or 30d). Useful for: (1) discovering what data sources are hot for current events, (2) confirming a popular tool is the canonical choice before asking your own question, (3) seeing whether your use case aligns with what most agents need. Self-aggregating signal — derived from CF analytics-engine, no PII, just (pack, tool, count). Cached 5min-1h depending on window. It is categorised as a Read tool in the Linear MCP Server, which means it retrieves data without modifying state.
pipeworx_trending accepts 1 parameter: window. 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 pipeworx_trending: 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.
pipeworx_trending 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 pipeworx_trending 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 pipeworx_trending. 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.
pipeworx_trending 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