搜索 GitHub 仓库。当我需要查找特定主题、功能或示例代码的仓库时，我会使用此工具。我会根据上下文自动构建合适的搜索关键词。
AI agents call github_search_repo to retrieve information from MCP Toolkit without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and queries data from GitHub—it searches for repositories matching criteria. It has no side effects, does not modify or delete data, does not execute code, and does not move money. It falls cleanly into the Read category as a search/discovery tool.
From the tool's definition Tool name 'github_search_repo' and description indicate searching/querying GitHub repositories ('搜索 GitHub 仓库' = 'search GitHub repositories').
Attacks that exploit this kind of access
搜索 GitHub 仓库。当我需要查找特定主题、功能或示例代码的仓库时，我会使用此工具。我会根据上下文自动构建合适的搜索关键词。. It is categorised as a Read tool in the MCP Toolkit MCP Server, which means it retrieves data without modifying state.
Register the MCP Toolkit MCP server in PolicyLayer and add a rule for github_search_repo: 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 MCP Toolkit. Nothing to install.
github_search_repo 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_search_repo 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_search_repo. 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_search_repo is provided by the MCP Toolkit MCP server (zxfgds/mcp-toolkit). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the 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 →