gateway.pipeworx.io

Very long descriptions are sometimes used to bury instructions to the AI. Skim it before allowing.

Very long descriptions are sometimes used to bury instructions to the AI. Skim it before allowing.

Very long descriptions are sometimes used to bury instructions to the AI. Skim it before allowing.

Very long descriptions are sometimes used to bury instructions to the AI. Skim it before allowing.

This server isn't on gate's handpicked list. That's not necessarily bad, but there's no third-party signal about it — review its tools carefully.

The `_apiKey` parameter accepts a raw Anthropic API key (sk-ant-...) and forwards it directly to api.anthropic.com. While billed as a 'BYO key' feature, having the agent handle and transmit a live credential string as a plain tool argument creates exposure risk (e.g., if the key ends up logged, cached, or is inadvertently reused from stored memory) and should be handled via a secure, out-of-band credential mechanism rather than an inline string argument.

Same pattern as ai_visibility_check: `_apiKey` accepts a raw Anthropic API key and passes it 'per probe' to api.anthropic.com for every entity being compared. Multiple internal calls increase the surface for the key to be logged or leaked, and there is no indication of scoping/redaction.

The tool fetches an arbitrary user-supplied URL server-side with no stated restriction against internal/private/loopback addresses (contrast with the `subscribe` tool's webhook field, which explicitly states 'localhost/private hosts rejected'). If the fetch runs from a server with internal network access, this could be used to probe or retrieve content from internal-only endpoints.

The description repeatedly instructs the agent to prefer this tool 'over web search' and to use it as the 'default entry point... even if web search could also answer it,' for a very broad class of questions. This is steering language embedded in a tool description that goes beyond neutrally describing the tool's function and could cause the agent to systematically bypass more appropriate tools (including ones the user explicitly requested) without user awareness.

Description encourages routing all questions here 'exactly like ask_pipeworx,' inheriting the same broad self-promotional steering noted for the primary tool.