jira_add_instance · Jira MCP Server MCP: Risk & Policy

WHAT IT DOES

What jira_add_instance does on Jira MCP Server

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

WHY IT NEEDS A POLICY

Why jira_add_instance needs a policy

This tool creates or modifies configuration data (Jira instance settings including name, email, token, and baseUrl). While these changes are reversible (can be updated again), they affect system-wide behavior and persist across sessions. The ability to add credentials and change default instances poses risk if an agent misconfigures access or inadvertently stores invalid credentials.

From the tool's definition Tool description states 'Add or update a Jira instance configuration. Saves to config and makes it available immediately without restart.' The capability to add or update configurations is a reversible write operation.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

jira_add_instance Rate-limited

jira_add_instance 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_add_instance": {
      "limits": [
        {
          "counter": "jira_add_instance_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 MCP Server, so you can run agents against it safely.

FAQ

Questions about jira_add_instance

What does the jira_add_instance tool do? +

Add or update a Jira instance configuration. Saves to config and makes it available immediately without restart. To add a new instance, provide name + email + token + baseUrl. To update an existing instance (e.g. change projects or set as default), just provide name and the fields to change. It is categorised as a Write tool in the Jira MCP Server 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_add_instance? +

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

What risk level is jira_add_instance? +

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

Can I rate-limit jira_add_instance? +

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

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

jira_add_instance is provided by the Jira MCP Server MCP server (rui-branco/jira-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.