Get overall system metrics including request counts and user statistics
AI agents call get-metrics to retrieve information from NestJS MCP Server Module without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and queries system metrics data. It performs a read-only operation returning aggregate statistics about system performance and user activity. There is no indication of data modification, deletion, code execution, financial impact, or destructive behavior. The minimal blast radius of misuse (exposure of system metrics) and lack of side effects places this in the Read category with low severity.
From the tool's definition Tool name 'get-metrics' and description 'Get overall system metrics including request counts and user statistics' indicate a retrieval operation with no modification or side effects.
Attacks that exploit this kind of access
Get overall system metrics including request counts and user statistics. It is categorised as a Read tool in the NestJS MCP Server Module MCP Server, which means it retrieves data without modifying state.
Register the NestJS MCP Server Module MCP server in PolicyLayer and add a rule for get-metrics: 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 Module. Nothing to install.
get-metrics 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-metrics 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-metrics. 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-metrics is provided by the NestJS MCP Server Module MCP server (rekog-labs/mcp-nest). 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 →