get_copilot_space
This tool can be used to provide additional context to the chat from a specific Copilot space. If the user mentions the keyword 'Copilot space' with the name and owner of the space, execute this tool. The response includes a table of contents (TOC) listing all documents in the space, followed by ...
This record as markdown: /tools/github/get-copilot-space.md
What get_copilot_space does on GitHub
AI agents call get_copilot_space 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 |
|---|---|---|---|
name | string | — | The name of the space |
owner | string | — | The owner of the space |
Parameters from the server's own tool schema.
Why get_copilot_space is rated Low
This tool performs a read-only retrieval operation of documents and metadata from a Copilot space. It has no side effects, does not modify data, execute code, delete content, or involve financial operations. The description explicitly indicates it 'provide[s] additional context' through content retrieval.
From the tool's definition The tool 'retrieves additional context from a specific Copilot space' and 'provides a table of contents...followed by the full content of each document.' It reads and returns document content without modification, deletion, or execution.
Attacks that exploit this kind of access
The rule that runs get_copilot_space 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_space, this is the rule to start with:
get_copilot_space is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect GitHub, apply this rule, and every get_copilot_space call is checked against it from then on.
Questions about get_copilot_space
This tool can be used to provide additional context to the chat from a specific Copilot space. If the user mentions the keyword 'Copilot space' with the name and owner of the space, execute this tool. The response includes a table of contents (TOC) listing all documents in the space, followed by the full content of each document. Documents are separated by markers in the format: '--- Document N: path (size) ---'. When searching for specific information, use grep (or equivalent command) to search across all documents; the separator lines will help identify which document contains the matching content. It is categorised as a Read tool in the GitHub MCP Server, which means it retrieves data without modifying state.
get_copilot_space accepts 2 parameters: name, owner. The full parameter table on this page comes from the server's own tool schema.
Register the GitHub MCP server in PolicyLayer and add a rule for get_copilot_space: 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.
get_copilot_space 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_copilot_space 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_copilot_space. 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_copilot_space 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.
More on GitHub, and thousands of servers like it.
This server
Across the catalogue