リポジトリのデプロイ頻度を取得します。デプロイ頻度はFour Keys（DORAメトリクス）の1つで、本番環境へのデプロイ頻度を測定します。
AI agents call get_deployment_frequency 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 data retrieval operation that queries deployment frequency metrics from a repository. It performs no modifications, deletions, or external operations. The tool only reads and returns metric information, consistent with other Read-category tools on this server like 'get_current_time', 'get_mttr', and 'get_lead_time'. Misuse poses minimal risk as it cannot alter data or trigger unintended actions.
From the tool's definition Tool name 'get_deployment_frequency' and description indicate it 'retrieves' (取得します) deployment frequency metrics.
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_deployment_frequency: 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_deployment_frequency 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_deployment_frequency 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_deployment_frequency. 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_deployment_frequency 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 →