AI agents call get_issues_by_type 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 or queries Jira issues filtered by type. It has no side effects—it only reads and returns existing data. There is no risk of data modification, deletion, code execution, or financial impact. The low severity reflects that misuse would only expose information that may already be accessible through normal Jira access controls.
From the tool's definition Tool name 'get_issues_by_type' and description 'Get issues of a specific type' indicate a retrieval operation with no modification, creation, or deletion of data.
Documented attack patterns abuse exactly the kind of access get_issues_by_type 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_issues_by_type:
{
"version": "1",
"default": "deny",
"tools": {
"get_issues_by_type": {}
}
}get_issues_by_type 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 issues of a specific type. 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_issues_by_type: 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_issues_by_type 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_issues_by_type 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_issues_by_type. 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_issues_by_type 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.