Low Risk

get_copilot_job_status

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 requ...

Part of the GitHub MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.

AI agents call get_copilot_job_status to retrieve information from GitHub without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.

Even though get_copilot_job_status only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.

Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.

github.yaml
tools:
  get_copilot_job_status:
    rules:
      - action: allow

See the full GitHub policy for all 86 tools.

Tool Name get_copilot_job_status
Category Read
MCP Server GitHub MCP Server
Risk Level Low

View all 86 tools →

Agents calling read-class tools like get_copilot_job_status have been implicated in these attack patterns. Read the full case and prevention policy for each:

Browse the full MCP Attack Database →

Other tools in the Read risk category across the catalogue. The same policy patterns (rate-limit, allow) apply to each.

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.

How do I enforce a policy on get_copilot_job_status? +

Add a rule in your Intercept YAML policy under the tools section for get_copilot_job_status. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the GitHub MCP server.

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 Intercept 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 Intercept 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 (@github/github-mcp-server). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policies on GitHub

Open source. One binary. Zero dependencies.

npx -y @policylayer/intercept
github.com/policylayer/intercept →
// GET IN TOUCH

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

Message sent.

We'll get back to you soon.