Get the combined status of all status checks for a pull request
AI agents call get_pull_request_status to retrieve information from MCP-Brave-Search without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries the status of pull request checks. It retrieves data (status information) without creating, modifying, deleting, or executing any operations. The verb 'Get' combined with the read-only nature of retrieving check statuses clearly places this in the Read category with low severity, as it poses minimal risk when accessed by an AI agent.
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 retrieval of status information without modification or side effects.
Documented attack patterns abuse exactly the kind of access get_pull_request_status gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and MCP-Brave-Search, and nothing reaches the server without passing your rules. This is the rule we recommend for get_pull_request_status:
{
"version": "1",
"default": "deny",
"tools": {
"get_pull_request_status": {}
}
} get_pull_request_status 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 the combined status of all status checks for a pull request. It is categorised as a Read tool in the MCP-Brave-Search MCP Server, which means it retrieves data without modifying state.
Register the MCP-Brave-Search 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 MCP-Brave-Search. 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 MCP-Brave-Search MCP server (modelcontextprotocol/servers-archived). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from MCP-Brave-Search, 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.
59 MCP-Brave-Search tools catalogued and risk-classified — across an index of 43,000+ MCP servers.