github_support_docs_search
Retrieve documentation relevant to answer GitHub product and support questions. Support topics include: GitHub Actions Workflows, Authentication, GitHub Support Inquiries, Pull Request Practices, Repository Maintenance, GitHub Pages, GitHub Packages, GitHub Discussions, Copilot Spaces
This record as markdown: /tools/github/github-support-docs-search.md
What github_support_docs_search does on GitHub
AI agents call github_support_docs_search 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 |
|---|---|---|---|
query | string | — | Input from the user about the question they need answered. This is the latest raw unedited user message. You should ALWAYS leave the user message as it is, you |
Parameters from the server's own tool schema.
Why github_support_docs_search is rated Low
This tool retrieves and searches through existing GitHub support documentation. It performs a read-only query operation with no ability to modify, delete, or execute code. The documentation retrieved is informational only. No side effects or risk of unintended consequences from an AI agent using this tool.
From the tool's definition Tool name contains 'search' and description states 'Retrieve documentation' — both indicate data retrieval without side effects. The tool queries support documentation to answer questions.
Risk signalsAccepts freeform code/query input (query)
Attacks that exploit this kind of access
The rule that runs github_support_docs_search 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 github_support_docs_search, this is the rule to start with:
github_support_docs_search 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 github_support_docs_search call is checked against it from then on.
Questions about github_support_docs_search
Retrieve documentation relevant to answer GitHub product and support questions. Support topics include: GitHub Actions Workflows, Authentication, GitHub Support Inquiries, Pull Request Practices, Repository Maintenance, GitHub Pages, GitHub Packages, GitHub Discussions, Copilot Spaces. It is categorised as a Read tool in the GitHub MCP Server, which means it retrieves data without modifying state.
github_support_docs_search accepts 1 parameter: query. 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 github_support_docs_search: 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.
github_support_docs_search 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 github_support_docs_search 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 github_support_docs_search. 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.
github_support_docs_search 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