AI agents call get_issue_types to retrieve information from Jira-Context-MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves configuration/reference data (available issue types) from Jira. It performs no side effects, creates no data, executes no commands, and poses no destructive or financial risk. The operation is purely informational and read-only, making it a clear Read category classification with low severity.
From the tool's definition Tool name 'get_issue_types' and description 'Get list of available Jira issue types' indicate a retrieval operation that queries and returns metadata about Jira issue types without modifying any data.
Documented attack patterns abuse exactly the kind of access get_issue_types gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Jira-Context-MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for get_issue_types:
{
"version": "1",
"default": "deny",
"tools": {
"get_issue_types": {}
}
}get_issue_types is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Get list of available Jira issue types. It is categorised as a Read tool in the Jira-Context-MCP MCP Server, which means it retrieves data without modifying state.
Register the Jira-Context- MCP server in PolicyLayer and add a rule for get_issue_types: 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-Context-MCP. Nothing to install.
get_issue_types is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_issue_types 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.
Set action: deny in the PolicyLayer policy for get_issue_types. 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.
get_issue_types is provided by the Jira-Context- MCP server (rahulthedevil/jira-context-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Jira-Context-MCP, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
5 Jira-Context-MCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.