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...
AI agents call pipeworx_trending to retrieve information from Mcp Themeparks without modifying anything — 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.
This is a pure read operation that queries and retrieves aggregated usage statistics. It has no side effects—it observes trends without altering system state, data, or triggering external operations. The low severity reflects minimal blast radius: misuse would only expose non-sensitive aggregate metrics about which tools are popular.
From the tool's definition Tool returns aggregated analytics: 'top tools', 'top packs', 'total call volume' over time windows. Description explicitly states 'no PII, just (pack, tool, count)' and data is 'derived from CF analytics-engine'.
Attacks that exploit this kind of access
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 Mcp Themeparks 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 Mcp Themeparks 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 Mcp Themeparks. 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 Mcp Themeparks MCP server (pipeworx-io/mcp-themeparks). 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 →