get_pull_request_status

Get the combined status of all status checks for a pull request

Server Helm Chart CLI jeff-nasseri/servers
Category Read
Risk class Low
Parameters 00 required

What get_pull_request_status does on Helm Chart CLI

AI agents call get_pull_request_status to retrieve information from Helm Chart CLI without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Why get_pull_request_status needs a policy

This tool retrieves and queries the status of pull request checks without creating, modifying, deleting, or executing any operations. It is a read-only operation with minimal security impact, suitable for information gathering about CI/CD pipeline status.

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 side effects. The verb 'Get' and lack of any modification language confirm this is a query operation.

Questions about get_pull_request_status

What does the get_pull_request_status tool do? +

Get the combined status of all status checks for a pull request. It is categorised as a Read tool in the Helm Chart CLI MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_pull_request_status? +

Register the Helm Chart CLI 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 Helm Chart CLI. Nothing to install.

What risk level is get_pull_request_status? +

get_pull_request_status is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_pull_request_status? +

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.

How do I block get_pull_request_status completely? +

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.

What MCP server provides get_pull_request_status? +

get_pull_request_status is provided by the Helm Chart CLI MCP server (jeff-nasseri/servers). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// LOOK UP ANOTHER 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 →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.