get_project_permission_scheme

THE RISK

Low Risk

Why get_project_permission_scheme needs a policy

This tool queries and retrieves existing permission scheme data for a Jira project. It performs a read-only operation that does not create, modify, delete, or execute any actions. The data retrieved is configuration metadata about project permissions, not sensitive user data that would warrant higher severity.

From the tool's definition Tool name 'get_project_permission_scheme' and description 'Get permission scheme for a project' indicate a retrieval operation with no modification or side effects.

Documented attack patterns abuse exactly the kind of access get_project_permission_scheme gives an agent:

POLICY

How to control get_project_permission_scheme

PolicyLayer is an MCP gateway — it sits between your AI agents and Jira MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for get_project_permission_scheme:

policy.json

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

get_project_permission_scheme is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

Create a free account and register Jira MCP Server — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

CAP THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Jira MCP Server tools

Destructive delete_comment Delete a comment from a Jira issue. Destructive delete_issue Delete a Jira issue (use with caution). Write remove_issue_labels Remove labels from a Jira issue. Write add_comment Add a comment to a Jira issue. Write add_issue_labels Add labels to a Jira issue. Write assign_issue Assign a Jira issue to a user. Write create_issue Create a new Jira issue. Write transition_issue Transition a Jira issue to a new status.

All 30 Jira MCP Server tools →

Read tools on other servers

M-Team MCP Server get_torrent_detail YouTube MCP Server search_channel Android Forensics ADB MCP Server parse_browser_history 0xarchive web3_challenge

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Data exfiltration → How read access becomes an exfiltration channel when chained with untrusted content.
MCP token cost → What connecting this server costs in context-window tokens on every request.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about get_project_permission_scheme

What does the get_project_permission_scheme tool do? +

Get permission scheme for a project. It is categorised as a Read tool in the Jira MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_project_permission_scheme? +

Register the Jira MCP Server MCP server in PolicyLayer and add a rule for get_project_permission_scheme: 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 get_project_permission_scheme? +

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

Can I rate-limit get_project_permission_scheme? +

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

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

get_project_permission_scheme is provided by the Jira MCP Server MCP server (redhat-community-ai-tools/jira-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Jira MCP Server tool call.

Start from Jira MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →