Get the latest version of an nf-core subworkflow.
AI agents call get_nfcore_subworkflow 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.
This tool retrieves metadata (latest version) of an nf-core subworkflow from a registry. It is a read-only query operation analogous to 'get' or 'fetch' endpoints. No data is modified, deleted, executed, or financially committed. The blast radius of misuse is minimal—an agent would only retrieve publicly available package metadata.
From the tool's definition Tool name 'get_nfcore_subworkflow' and description 'Get the latest version of an nf-core subworkflow' indicate a query/retrieval operation with no side effects. The server description confirms it 'queries 19 package registries...
Attacks that exploit this kind of access
Get the latest version of an nf-core subworkflow. 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_nfcore_subworkflow: 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_nfcore_subworkflow 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_nfcore_subworkflow 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_nfcore_subworkflow. 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_nfcore_subworkflow 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 →