Get Terragrunt MCP server metrics: cache hit rates, tool invocation counts, response times, and memory usage for observability.
AI agents call get_server_metrics to retrieve information from Terragrunt MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool only queries and returns observability metrics about the MCP server itself. It has no side effects, does not modify data, execute code, delete resources, or commit financial obligations. It is a straightforward telemetry/monitoring function with minimal security risk.
From the tool's definition Tool retrieves metrics data (cache hit rates, tool invocation counts, response times, memory usage) with no modification of state or execution of external operations.
Attacks that exploit this kind of access
Get Terragrunt MCP server metrics: cache hit rates, tool invocation counts, response times, and memory usage for observability. It is categorised as a Read tool in the Terragrunt MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Terragrunt MCP Server MCP server in PolicyLayer and add a rule for get_server_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 Terragrunt MCP Server. Nothing to install.
get_server_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_server_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_server_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_server_metrics is provided by the Terragrunt MCP Server MCP server (omattsson/terragrunt-mcp-server). 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 →