リポジトリのMTTR（平均復旧時間）を取得します。MTTRはFour Keys（DORAメトリクス）の1つで、障害発生から復旧までの平均時間を測定します。
AI agents call get_mttr to retrieve information from NestJS MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and retrieves Mean Time To Recovery (MTTR) metrics from a repository—a standard DORA metric. It performs data retrieval without modifying, deleting, or executing external operations. The Japanese description 'リポジトリのMTTR（平均復旧時間）を取得します' confirms it fetches existing metric data. No destructive, financial, or execution capabilities are present. This is a straightforward Read operation.
From the tool's definition Tool name is 'get_mttr' and description states it 'retrieves' (取得します) MTTR metrics. The verb 'get' and the context of retrieving performance metrics from a repository indicate a read-only operation with no side effects.
Attacks that exploit this kind of access
リポジトリのMTTR（平均復旧時間）を取得します。MTTRはFour Keys（DORAメトリクス）の1つで、障害発生から復旧までの平均時間を測定します。. It is categorised as a Read tool in the NestJS MCP Server MCP Server, which means it retrieves data without modifying state.
Register the NestJS MCP Server MCP server in PolicyLayer and add a rule for get_mttr: 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 NestJS MCP Server. Nothing to install.
get_mttr 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_mttr 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_mttr. 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_mttr is provided by the NestJS MCP Server MCP server (kaz29/mcp-server-example). 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 →