AI-powered 100-point project health score: analyses unresolved bugs, stale issues, sprint velocity, and unassigned work.
AI agents call jira_health_check to retrieve information from RedisNexus without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and evaluates project health data from Jira without modifying state, executing operations, or triggering external actions. It performs read-only analysis to generate a health score. The blast radius of misuse is minimal—an agent could only obtain insights about project status, which does not compromise data integrity or systems.
From the tool's definition Tool description states it 'analyses' metrics (unresolved bugs, stale issues, sprint velocity, unassigned work) without any modification or execution capabilities. The term 'health_check' and 'analyses' indicate data retrieval and assessment only.
Attacks that exploit this kind of access
AI-powered 100-point project health score: analyses unresolved bugs, stale issues, sprint velocity, and unassigned work. It is categorised as a Read tool in the RedisNexus MCP Server, which means it retrieves data without modifying state.
Register the RedisNexus MCP server in PolicyLayer and add a rule for jira_health_check: 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 RedisNexus. Nothing to install.
jira_health_check 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 jira_health_check 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 jira_health_check. 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.
jira_health_check is provided by the RedisNexus MCP server (rajkumar-madhu/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →