get_ovnk_latency_metrics

get_ovnk_latency_metrics

Server OpenShift OVN-Kubernetes Benchmark MCP Server liqcui/ovnk-benchmark-mcp
Category Read
Risk class Low
Parameters 00 required

What get_ovnk_latency_metrics does on OpenShift OVN-Kubernetes Benchmark MCP Server

AI agents call get_ovnk_latency_metrics to retrieve information from OpenShift OVN-Kubernetes Benchmark MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Why get_ovnk_latency_metrics needs a policy

The 'get_' prefix and naming pattern consistent with other metrics retrieval tools on this benchmarking server indicate this tool retrieves latency data without modification or execution. Despite the empty description limiting direct evidence, the tool context and sibling tools all perform read-only monitoring and analysis operations typical of observability platforms.

From the tool's definition Tool name 'get_ovnk_latency_metrics' indicates data retrieval (get prefix) of performance metrics. Sibling tools on the server are all query/analysis/monitoring operations with no side effects (query_cluster_node_usage, query_kube_api_metrics,…

Questions about get_ovnk_latency_metrics

What does the get_ovnk_latency_metrics tool do? +

get_ovnk_latency_metrics. It is categorised as a Read tool in the OpenShift OVN-Kubernetes Benchmark MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_ovnk_latency_metrics? +

Register the OpenShift OVN-Kubernetes Benchmark MCP Server MCP server in PolicyLayer and add a rule for get_ovnk_latency_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 OpenShift OVN-Kubernetes Benchmark MCP Server. Nothing to install.

What risk level is get_ovnk_latency_metrics? +

get_ovnk_latency_metrics is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_ovnk_latency_metrics? +

Yes. Add a rate_limit block to the get_ovnk_latency_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.

How do I block get_ovnk_latency_metrics completely? +

Set action: deny in the PolicyLayer policy for get_ovnk_latency_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.

What MCP server provides get_ovnk_latency_metrics? +

get_ovnk_latency_metrics is provided by the OpenShift OVN-Kubernetes Benchmark MCP Server MCP server (liqcui/ovnk-benchmark-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// LOOK UP ANOTHER 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 →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.