jira_list_projects

List all Jira projects

SERVERScopeGate SOURCEhttps://mcp.scopegate.cloud/{api_key}

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/io-github-alifanov-scopegate/jira-list-projects.md

WHAT IT DOES

What jira_list_projects does on ScopeGate

AI agents call jira_list_projects to retrieve information from ScopeGate 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_projects is rated Low

This tool queries and returns project metadata from Jira without creating, modifying, deleting, or executing any operations. It is a straightforward read operation with minimal risk unless the project list itself is considered highly sensitive in a given context.

From the tool's definition Tool name contains 'list' and description states 'List all Jira projects' — a pure retrieval operation with no side effects.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs jira_list_projects safely

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

jira_list_projects Allowed

jira_list_projects 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_projects": {}
  }
}

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

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

FAQ

Questions about jira_list_projects

What does the jira_list_projects tool do? +

List all Jira projects. It is categorised as a Read tool in the ScopeGate MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on jira_list_projects? +

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

What risk level is jira_list_projects? +

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

Can I rate-limit jira_list_projects? +

Yes. Add a rate_limit block to the jira_list_projects 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_projects completely? +

Set action: deny in the PolicyLayer policy for jira_list_projects. 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_projects? +

jira_list_projects is provided by the ScopeGate MCP server (https://mcp.scopegate.cloud/{api_key}). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on ScopeGate, and thousands of servers like it.

This server

All 385 ScopeGate tools →

Across the catalogue

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

Guides

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