jira_list_versions

List versions/releases for a project

SERVERSage MCP SOURCEsagemcp/sagemcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/sagemcp-sagemcp/jira-list-versions.md

WHAT IT DOES

What jira_list_versions does on Sage MCP

AI agents call jira_list_versions to retrieve information from Sage MCP without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why jira_list_versions is rated Low

This tool performs a query operation that retrieves project version information with no side effects, data modification, or external state changes. It falls squarely into the Read category with low severity since version listing is informational only and poses minimal risk even if misused by an AI agent.

From the tool's definition Tool name 'jira_list_versions' and description 'List versions/releases for a project' indicate a read-only operation that retrieves and lists existing version/release data without modification.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs jira_list_versions safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Sage MCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For jira_list_versions, this is the rule to start with:

jira_list_versions Allowed

jira_list_versions is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "jira_list_versions": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Sage MCP, apply this rule, and every jira_list_versions call is checked against it from then on.

FAQ

Questions about jira_list_versions

What does the jira_list_versions tool do? +

List versions/releases for a project. It is categorised as a Read tool in the Sage MCP MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on jira_list_versions? +

Register the Sage MCP server in PolicyLayer and add a rule for jira_list_versions: 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 Sage MCP. Nothing to install.

What risk level is jira_list_versions? +

jira_list_versions is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit jira_list_versions? +

Yes. Add a rate_limit block to the jira_list_versions 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.

How do I block jira_list_versions completely? +

Set action: deny in the PolicyLayer policy for jira_list_versions. 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.

What MCP server provides jira_list_versions? +

jira_list_versions is provided by the Sage MCP server (sagemcp/sagemcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Sage, and thousands of servers like it.

This server

All 359 Sage tools →

Across the catalogue

aiva_list_affiliates on AIVA MCP Server →list_circuits on 0gzk →list_agents on 0rca Dojo MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →