Get the latest version of a Nextflow pipeline from nf-core.
AI agents call get_nextflow_pipeline to retrieve information from Versionator without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool queries a package registry (nf-core) to retrieve version and metadata information. There are no side effects, no code execution, no data modification, and no destructive operations. This is purely a Read operation with minimal blast radius — worst case, an AI agent receives incorrect or stale package version information, which is low-severity.
From the tool's definition Tool description states 'Get the latest version of a Nextflow pipeline from nf-core' — retrieves metadata about pipeline versions without modifying, deleting, or executing code.
Attacks that exploit this kind of access
Get the latest version of a Nextflow pipeline from nf-core. It is categorised as a Read tool in the Versionator MCP Server, which means it retrieves data without modifying state.
Register the Versionator MCP server in PolicyLayer and add a rule for get_nextflow_pipeline: 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 Versionator. Nothing to install.
get_nextflow_pipeline 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 get_nextflow_pipeline 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 get_nextflow_pipeline. 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.
get_nextflow_pipeline is provided by the Versionator MCP server (trianglegrrl/versionator-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 →