リポジトリのFour Keys（DORAメトリクス）を一度に取得します。デプロイ頻度、リードタイム、変更失敗率、MTTRの全4つのメトリクスを集計し、総合的なパフォーマンスレベルを評価します。
AI agents call get_four_keys_summary 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 and aggregates performance metrics for display/analysis purposes. It has no side effects, creates no new data, executes no code, and deletes nothing. The function is purely informational, making it a Read category tool with low severity since misuse by an AI agent would only expose metrics data without operational impact.
From the tool's definition Tool name 'get_four_keys_summary' and description indicate retrieval of Four Keys metrics (deployment frequency, lead time, change failure rate, MTTR).
Attacks that exploit this kind of access
リポジトリのFour Keys（DORAメトリクス）を一度に取得します。デプロイ頻度、リードタイム、変更失敗率、MTTRの全4つのメトリクスを集計し、総合的なパフォーマンスレベルを評価します。. 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_four_keys_summary: 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_four_keys_summary 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_four_keys_summary 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_four_keys_summary. 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_four_keys_summary 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 →