リポジトリの変更失敗率を取得します。変更失敗率はFour Keys（DORAメトリクス）の1つで、デプロイ後に障害が発生した割合を測定します。
AI agents call get_change_failure_rate 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 retrieves metrics data about repository deployment failures. It performs a read-only query operation to fetch pre-calculated or aggregated metrics (Four Keys/DORA metrics). There are no side effects, no code execution, no data modification, and no irreversible actions. The low severity reflects minimal risk even if misused—an agent could only retrieve metrics information without operational impact.
From the tool's definition Tool name 'get_change_failure_rate' and description explicitly state it 'retrieves' (取得します) the change failure rate metric.
Attacks that exploit this kind of access
リポジトリの変更失敗率を取得します。変更失敗率は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_change_failure_rate: 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_change_failure_rate 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_change_failure_rate 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_change_failure_rate. 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_change_failure_rate 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 →