Get the combined status of all status checks for a pull request
AI agents call get_pull_request_status to retrieve information from GitHub See MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves status information about pull request checks. It performs a query operation that returns data without creating, modifying, deleting, or executing any actions. The verb 'Get' and the read-only nature of status checking align with the Read category.
From the tool's definition Tool name 'get_pull_request_status' and description 'Get the combined status of all status checks for a pull request' indicate a retrieval operation with no modification or side effects.
Attacks that exploit this kind of access
Get the combined status of all status checks for a pull request. It is categorised as a Read tool in the GitHub See MCP Server MCP Server, which means it retrieves data without modifying state.
Register the GitHub See MCP Server MCP server in PolicyLayer and add a rule for get_pull_request_status: 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 See MCP Server. Nothing to install.
get_pull_request_status 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_pull_request_status 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_pull_request_status. 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_pull_request_status is provided by the GitHub See MCP Server MCP server (jesusmaster/github-see-mcp-server). 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 →