analyze_github_repo · Time Complexity MCP: Risk & Policy

WHAT IT DOES

What analyze_github_repo does on Time Complexity

AI agents invoke analyze_github_repo to trigger actions in Time Complexity. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.

WHY IT NEEDS A POLICY

Why analyze_github_repo needs a policy

This tool executes shell-level git operations (cloning a remote repository) and then performs filesystem-level analysis. It triggers external operations (network fetch, disk writes for the clone) whose effects depend on the supplied URL argument. An adversary could supply a malicious or enormous repository URL, causing unexpected disk usage, network activity, or execution of hooks.

From the tool's definition 'Clone a GitHub repository' and 'Requires git in PATH' — the tool runs git commands to clone an external repository and then executes static analysis across the codebase

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

analyze_github_repo Rate-limited

analyze_github_repo stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "analyze_github_repo": {
      "limits": [
        {
          "counter": "analyze_github_repo_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Time Complexity, so you can run agents against it safely.

FAQ

Questions about analyze_github_repo

What does the analyze_github_repo tool do? +

Clone a GitHub repository and analyze complexity across the codebase. Accepts full URL (https://github.com/owner/repo) or shorthand (owner/repo). Requires git in PATH. Returns per-file complexity with hotspots, plus repository metadata. It is categorised as a Execute tool in the Time Complexity MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on analyze_github_repo? +

Register the Time Complexity MCP server in PolicyLayer and add a rule for analyze_github_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 Time Complexity. Nothing to install.

What risk level is analyze_github_repo? +

analyze_github_repo is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit analyze_github_repo? +

Yes. Add a rate_limit block to the analyze_github_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.

How do I block analyze_github_repo completely? +

Set action: deny in the PolicyLayer policy for analyze_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 analyze_github_repo? +

analyze_github_repo is provided by the Time Complexity MCP server (luzgan/time-complexity-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.