get_copilot_job_status

SERVERGitHub SOURCEoci:ghcr.io/github/github-mcp-server:1.3.0

Low RISK CLASS

Category Read

Parameters 30 required

Recommended Allowedsee the rule below

Registry record Grade D, identity verified Pull the record →

This record as markdown: /tools/github/get-copilot-job-status.md

WHAT IT DOES

What get_copilot_job_status does on GitHub

AI agents call get_copilot_job_status to retrieve information from GitHub without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Parameter	Type	Required	Description
`id`	string	—	Job ID or pull request number
`repo`	string	—	Repository name
`owner`	string	—	Repository owner

Parameters from the server's own tool schema.

RISK

Why get_copilot_job_status is rated Low

This tool retrieves status information about an existing job or pull request without modifying, executing, or deleting any data. It is purely informational (get/check), returning job status and pull request URLs as query results with no side effects.

From the tool's definition Get the status of a GitHub Copilot coding agent job. Use this to check if a previously submitted task has completed and to get the pull request URL once it's created.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs get_copilot_job_status safely

PolicyLayer is an MCP gateway: it sits between your AI agents and GitHub, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_copilot_job_status, this is the rule to start with:

get_copilot_job_status Allowed

get_copilot_job_status is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_copilot_job_status": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect GitHub, apply this rule, and every get_copilot_job_status call is checked against it from then on.

FAQ

Questions about get_copilot_job_status

What does the get_copilot_job_status tool do? +

Get the status of a GitHub Copilot coding agent job. Use this to check if a previously submitted task has completed and to get the pull request URL once it's created. Provide the job ID (from create_pull_request_with_copilot) or pull request number (from assign_copilot_to_issue), or any pull request you want agent sessions for. It is categorised as a Read tool in the GitHub MCP Server, which means it retrieves data without modifying state.

What parameters does get_copilot_job_status accept? +

get_copilot_job_status accepts 3 parameters: id, repo, owner. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on get_copilot_job_status? +

Register the GitHub MCP server in PolicyLayer and add a rule for get_copilot_job_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. Nothing to install.

What risk level is get_copilot_job_status? +

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

Can I rate-limit get_copilot_job_status? +

Yes. Add a rate_limit block to the get_copilot_job_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_copilot_job_status completely? +

Set action: deny in the PolicyLayer policy for get_copilot_job_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_copilot_job_status? +

get_copilot_job_status is provided by the GitHub MCP server (oci:ghcr.io/github/github-mcp-server:1.3.0). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on GitHub, and thousands of servers like it.

This server

All 86 GitHub tools →

Across the catalogue

get_task_status on 0rca Dojo MCP Server →get_cocktail_by_category on Cocktails RAG MCP Server →get_torrent_detail on M-Team MCP Server →aiva_get_affiliate on AIVA MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →