generate_activity_chart · GitHub Repository Analyzer MCP

WHAT IT DOES

What generate_activity_chart does on GitHub Repository Analyzer

AI agents use generate_activity_chart to create or update resources in GitHub Repository Analyzer — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your GitHub Repository Analyzer environment.

WHY IT NEEDS A POLICY

Why generate_activity_chart needs a policy

This tool creates/generates a new visualization artifact (a chart), which constitutes a Write operation. However, the severity is low because the action is non-destructive, reversible, and produces only a display output with no side effects on the repository itself, its data, or external systems. The chart generation is confined to rendering analysis results and does not modify repository state or data.

From the tool's definition Tool name 'generate_activity_chart' and description 'Create a visual chart' indicate generation of new content (a chart artifact). The tool produces output that is created/rendered, not merely read from existing sources.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

generate_activity_chart Rate-limited

generate_activity_chart stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "generate_activity_chart": {
      "limits": [
        {
          "counter": "generate_activity_chart_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

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

FAQ

Questions about generate_activity_chart

What does the generate_activity_chart tool do? +

Create a visual chart of repository commit activity. It is categorised as a Write tool in the GitHub Repository Analyzer MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on generate_activity_chart? +

Register the GitHub Repository Analyzer MCP server in PolicyLayer and add a rule for generate_activity_chart: 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 Repository Analyzer. Nothing to install.

What risk level is generate_activity_chart? +

generate_activity_chart is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit generate_activity_chart? +

Yes. Add a rate_limit block to the generate_activity_chart 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 generate_activity_chart completely? +

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

generate_activity_chart is provided by the GitHub Repository Analyzer MCP server (jar285/github_mcp_analyzer). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.