search-pipelines
AI agents call search-pipelines to retrieve information from nf-core MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool searches existing nf-core pipeline repositories—a read-only query operation with no data modification, deletion, or execution capabilities. The empty description reduces confidence slightly, but context from the server description and sibling tools strongly suggests a safe information retrieval function. No financial, destructive, or code-execution implications.
From the tool's definition Tool name 'search-pipelines' combined with server's stated purpose of 'list, search, and explore operations on pipeline configurations' indicates a query/search operation.
Attacks that exploit this kind of access
search-pipelines. It is categorised as a Read tool in the nf-core MCP Server MCP Server, which means it retrieves data without modifying state.
Register the nf-core MCP Server MCP server in PolicyLayer and add a rule for search-pipelines: 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 nf-core MCP Server. Nothing to install.
search-pipelines 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 search-pipelines 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 search-pipelines. 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.
search-pipelines is provided by the nf-core MCP Server MCP server (wjlim/nf-core_mcp). 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 →