get_etcd_disk_backend_commit

get_etcd_disk_backend_commit

Server OCP Performance Analyzer MCP openshift-eng/ocp-performance-analyzer-mcp
Category Read
Risk class Low
Parameters 00 required

What get_etcd_disk_backend_commit does on OCP Performance Analyzer MCP

AI agents call get_etcd_disk_backend_commit to retrieve information from OCP Performance Analyzer MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Why get_etcd_disk_backend_commit needs a policy

The 'get_' prefix consistently denotes read-only queries across the OCP Performance Analyzer suite. This tool retrieves etcd disk backend commit metrics for monitoring/analysis purposes, with no side effects. Even though the description is missing, the naming pattern and context of performance analysis tools (where data retrieval is the primary function) support a Read classification.

From the tool's definition Tool name 'get_etcd_disk_backend_commit' uses the verb 'get', indicating data retrieval. Description is empty, but the sibling tools (get_etcd_cluster_status, get_etcd_general_info, etc.) are all Read operations that query etcd cluster state without…

Questions about get_etcd_disk_backend_commit

What does the get_etcd_disk_backend_commit tool do? +

get_etcd_disk_backend_commit. It is categorised as a Read tool in the OCP Performance Analyzer MCP MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_etcd_disk_backend_commit? +

Register the OCP Performance Analyzer MCP server in PolicyLayer and add a rule for get_etcd_disk_backend_commit: 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 OCP Performance Analyzer MCP. Nothing to install.

What risk level is get_etcd_disk_backend_commit? +

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

Can I rate-limit get_etcd_disk_backend_commit? +

Yes. Add a rate_limit block to the get_etcd_disk_backend_commit 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_etcd_disk_backend_commit completely? +

Set action: deny in the PolicyLayer policy for get_etcd_disk_backend_commit. 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_etcd_disk_backend_commit? +

get_etcd_disk_backend_commit is provided by the OCP Performance Analyzer MCP server (openshift-eng/ocp-performance-analyzer-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.