list_check_runs
AI agents call list_check_runs to retrieve information from GitHub MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool name 'list_check_runs' indicates it retrieves a list of check runs (CI/CD status checks on pull requests or commits) from the GitHub API. This is a non-destructive query operation with no side effects. Despite the empty description lowering confidence slightly, the naming convention and context of sibling tools make the Read classification highly probable.
From the tool's definition Tool name 'list_check_runs' follows the 'list_*' pattern which retrieves or queries data without side effects. Sibling tools on this server include 'cancel_workflow_run', 'create_issue', and 'create_pr_review', which are higher-risk actions.
Attacks that exploit this kind of access
list_check_runs. It is categorised as a Read tool in the GitHub MCP Server MCP Server, which means it retrieves data without modifying state.
Register the GitHub MCP Server MCP server in PolicyLayer and add a rule for list_check_runs: 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 GitHub MCP Server. Nothing to install.
list_check_runs 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 list_check_runs 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 list_check_runs. 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.
list_check_runs is provided by the GitHub MCP Server MCP server (software-engineer-mj/github-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 →