Get details about a specific repository
AI agents call get_repository to retrieve information from GitHub MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves repository metadata and information without modifying, executing, or deleting anything. It is a straightforward read operation consistent with GitHub's public repository query API. The blast radius of misuse is minimal—an agent could only view repository details it has access to, with no destructive or financial consequences.
From the tool's definition Tool name 'get_repository' and description 'Get details about a specific repository' indicate a retrieval operation with no side effects. Confirmed by sibling tools: create_issue and list_issues are Write/Read, while this performs only data retrieval.
Attacks that exploit this kind of access
Get details about a specific repository. It is categorised as a Read tool in the GitHub MCP Server MCP Server, which means it retrieves data without modifying state.
Register the GitHub MCP Server MCP server in PolicyLayer and add a rule for get_repository: 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 MCP Server. Nothing to install.
get_repository 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_repository 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_repository. 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_repository is provided by the GitHub MCP Server MCP server (mdabdullahfaruque/github-mcp-server). 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 →