get_github_repository_info
AI agents call get_github_repository_info to retrieve information from DCI MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Based on the tool name alone, this appears to retrieve metadata or information about GitHub repositories without modifying, executing, or deleting anything. The 'get_' prefix is characteristic of Read operations. The empty description reduces confidence slightly, but the naming pattern and context of an integrated analysis/reporting server make a Read classification most appropriate.
From the tool's definition Tool name 'get_github_repository_info' indicates a retrieval operation. The description is empty, limiting direct evidence, but the naming convention and the context of sibling tools (which include read operations like 'download_dci_file',…
Attacks that exploit this kind of access
get_github_repository_info. It is categorised as a Read tool in the DCI MCP Server MCP Server, which means it retrieves data without modifying state.
Register the DCI MCP Server MCP server in PolicyLayer and add a rule for get_github_repository_info: 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 DCI MCP Server. Nothing to install.
get_github_repository_info 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_github_repository_info 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_github_repository_info. 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_github_repository_info is provided by the DCI MCP Server MCP server (redhat-community-ai-tools/dci-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 →