リポジトリのリードタイム（Lead Time for Changes）を取得します。リードタイムはFour Keys（DORAメトリクス）の1つで、コード変更が本番環境に反映されるまでの時間を測定します。具体的には、PRの作成からマージまでの時間を計測します。
AI agents call get_lead_time 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 is a metrics retrieval tool that queries repository data to calculate and return lead time statistics. It has no side effects, creates no new data, executes no code, and performs no destructive operations. It is a pure read operation consistent with other sibling tools like 'get_current_time', 'get_mttr', and 'list_notes'.
From the tool's definition Tool name 'get_lead_time' and description 'リポジトリのリードタイム（Lead Time for Changes）を取得します' ("retrieves/gets the lead time") - the verb 取得します means 'retrieves/obtains'.
Attacks that exploit this kind of access
リポジトリのリードタイム（Lead Time for Changes）を取得します。リードタイムはFour Keys（DORAメトリクス）の1つで、コード変更が本番環境に反映されるまでの時間を測定します。具体的には、PRの作成からマージまでの時間を計測します。. 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_lead_time: 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_lead_time 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_lead_time 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_lead_time. 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_lead_time 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 →