Comprehensive repository health check: activity, CI status, PR hygiene, issue triage, release cadence.
AI agents call gh_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 analyzes repository health metrics across multiple dimensions (activity, CI status, PR metrics, issues, releases). All described operations are informational checks that provide visibility into repository state without creating, modifying, deleting, or executing any code. No side effects on the repository or external systems are indicated. This is a typical monitoring/observability tool.
From the tool's definition Tool description states 'Comprehensive repository health check' with actions limited to checking 'activity, CI status, PR hygiene, issue triage, release cadence' — all read-only diagnostic operations that query and report on repository metadata without…
Attacks that exploit this kind of access
Comprehensive repository health check: activity, CI status, PR hygiene, issue triage, release cadence. 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 gh_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.
gh_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 gh_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 gh_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.
gh_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 →