jira_set_project_path · Jira Dev MCP: Risk & Policy

WHAT IT DOES

What jira_set_project_path does on Jira Dev

AI agents use jira_set_project_path to create or update resources in Jira Dev — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Jira Dev environment.

WHY IT NEEDS A POLICY

Why jira_set_project_path needs a policy

This tool creates or modifies a configuration mapping (project key to local path) but does not delete it irreversibly (Destructive), execute code (Execute), move money (Financial), or merely read data (Read). It is reversible—the mapping can be changed or reconfigured.

From the tool's definition Tool description states it 'Map[s] a Jira project key to a local repository path', which is a configuration operation that creates or modifies a mapping. The word 'Map' indicates establishing a stored association between project and path.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

jira_set_project_path Rate-limited

jira_set_project_path stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "jira_set_project_path": {
      "limits": [
        {
          "counter": "jira_set_project_path_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Jira Dev, so you can run agents against it safely.

FAQ

Questions about jira_set_project_path

What does the jira_set_project_path tool do? +

Map a Jira project key to a local repository path. This enables jira_read_task to include the local path hint for code exploration. It is categorised as a Write tool in the Jira Dev MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on jira_set_project_path? +

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

What risk level is jira_set_project_path? +

jira_set_project_path is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit jira_set_project_path? +

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

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

jira_set_project_path is provided by the Jira Dev MCP server (jira-dev-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.