get_metrics
Get a DenkOps project's request metrics (latency percentiles, error rate), latest resource sample, and rejected-request count over the last 24h.
This record as markdown: /tools/denkopsai-mcp/get-metrics.md
What get_metrics does on Denkopsai
AI agents call get_metrics to retrieve information from Denkopsai without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
project_id | string | Yes |
Parameters from the server's own tool schema.
Why get_metrics is rated Low
This tool only queries and retrieves monitoring/observability data about a DenkOps project. It performs no mutations, executions, deletions, or financial operations. The data returned is read-only diagnostic information used for understanding system performance over the last 24 hours. The blast radius of misuse is minimal—an attacker gains visibility into performance metrics but cannot alter infrastructure or data.
From the tool's definition Tool name 'get_metrics' and description explicitly states it retrieves metrics (latency percentiles, error rate, resource samples, rejected-request counts) with no modification or side effects implied.
Attacks that exploit this kind of access
The rule that runs get_metrics safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Denkopsai, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_metrics, this is the rule to start with:
get_metrics is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Denkopsai, apply this rule, and every get_metrics call is checked against it from then on.
Questions about get_metrics
Get a DenkOps project's request metrics (latency percentiles, error rate), latest resource sample, and rejected-request count over the last 24h. It is categorised as a Read tool in the Denkopsai MCP Server, which means it retrieves data without modifying state.
get_metrics accepts 1 parameter: project_id. Required: project_id. The full parameter table on this page comes from the server's own tool schema.
Register the Denkopsai 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 Denkopsai. 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 Denkopsai MCP server (@denkopsai/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Denkopsai, and thousands of servers like it.
This server
Across the catalogue