Low Risk

get_github_repo

Get GitHub repository details

Part of the Developer Tools MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.

AI agents call get_github_repo to retrieve information from Developer Tools without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.

Even though get_github_repo only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.

Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.

io-github-thenextgennexus-developer-tools-mcp-server.yaml
tools:
  get_github_repo:
    rules:
      - action: allow

See the full Developer Tools policy for all 7 tools.

Tool Name get_github_repo
Category Read
Risk Level Low

Agents calling read-class tools like get_github_repo have been implicated in these attack patterns. Read the full case and prevention policy for each:

Browse the full MCP Attack Database →

Other tools in the Read risk category across the catalogue. The same policy patterns (rate-limit, allow) apply to each.

What does the get_github_repo tool do? +

Get GitHub repository details. It is categorised as a Read tool in the Developer Tools MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_github_repo? +

Add a rule in your Intercept YAML policy under the tools section for get_github_repo. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Developer Tools MCP server.

What risk level is get_github_repo? +

get_github_repo is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_github_repo? +

Yes. Add a rate_limit block to the get_github_repo rule in your Intercept 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.

How do I block get_github_repo completely? +

Set action: deny in the Intercept policy for get_github_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.

What MCP server provides get_github_repo? +

get_github_repo is provided by the Developer Tools MCP server (@thenextgennexus/developer-tools-mcp-server). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policies on Developer Tools

Open source. One binary. Zero dependencies.

npx -y @policylayer/intercept
github.com/policylayer/intercept →
// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.