mttr_breakdown_analyzer
As a CTO, analyze your team's incident response efficiency by breaking down Mean Time To Recovery (MTTR) into root causes: code defects, infrastructure failures, or process bottlenecks. This tool ingests GitHub issue and pull request data alongside Snyk vulnerability reports to provide a detailed...
This record as markdown: /tools/io-github-getgapup-mcp-knowledge/mttr-breakdown-analyzer.md
What mttr_breakdown_analyzer does on Mcp Knowledge
AI agents call mttr_breakdown_analyzer to retrieve information from Mcp Knowledge without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
repo | string | Yes | Full GitHub repository name (owner/repo) |
async | boolean | — | If true, returns a job_id immediately (<200ms) instead of waiting for the result. Poll the result with job_result(job_id). Use for slow tools to avoid client ti |
since | string | Yes | Start date for analysis (ISO 8601) |
until | string | Yes | End date for analysis (ISO 8601) |
snykToken | string | — | Snyk API token for vulnerability data (optional) |
githubToken | string | Yes | GitHub personal access token for API access |
Parameters from the server's own tool schema.
Why mttr_breakdown_analyzer is rated Low
The tool reads and analyzes existing data from GitHub and Snyk to produce a structured report. It does not modify, delete, or execute anything — it retrieves and analyzes incident data to surface insights. Severity is medium because it accesses potentially sensitive security vulnerability reports (Snyk) and repository data, which could expose internal weaknesses if misused.
From the tool's definition analyze your team's incident response efficiency by breaking down Mean Time To Recovery (MTTR)... ingests GitHub issue and pull request data alongside Snyk vulnerability reports to provide a detailed breakdown
Risk signalsAdmin/system-level operation
Attacks that exploit this kind of access
The rule that runs mttr_breakdown_analyzer safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Mcp Knowledge, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For mttr_breakdown_analyzer, this is the rule to start with:
mttr_breakdown_analyzer is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Mcp Knowledge, apply this rule, and every mttr_breakdown_analyzer call is checked against it from then on.
Questions about mttr_breakdown_analyzer
As a CTO, analyze your team's incident response efficiency by breaking down Mean Time To Recovery (MTTR) into root causes: code defects, infrastructure failures, or process bottlenecks. This tool ingests GitHub issue and pull request data alongside Snyk vulnerability reports to provide a detailed breakdown of MTTR components, helping you identify systemic weaknesses in your incident resolution pipeline. Input your GitHub repository details and time range to receive a structured analysis of MTTR contributors with actionable insights. It is categorised as a Read tool in the Mcp Knowledge MCP Server, which means it retrieves data without modifying state.
mttr_breakdown_analyzer accepts 6 parameters: repo, async, since, until, snykToken, githubToken. Required: repo, since, until, githubToken. The full parameter table on this page comes from the server's own tool schema.
Register the Mcp Knowledge MCP server in PolicyLayer and add a rule for mttr_breakdown_analyzer: 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 Mcp Knowledge. Nothing to install.
mttr_breakdown_analyzer 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 mttr_breakdown_analyzer 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 mttr_breakdown_analyzer. 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.
mttr_breakdown_analyzer is provided by the Mcp Knowledge MCP server (https://mcp.gapup.io). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Mcp Knowledge, and thousands of servers like it.
This server
Across the catalogue