get_machine_config_pool_status
AI agents call get_machine_config_pool_status to retrieve information from Lumino MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The 'get_' prefix and 'status' suffix strongly indicate this tool queries or retrieves state information from Kubernetes/OpenShift machine config pools without modifying them. In the context of an SRE observability platform, this aligns with diagnostic/monitoring capabilities.
From the tool's definition Tool name 'get_machine_config_pool_status' uses 'get' prefix, indicating a read operation that retrieves status information about machine config pools. No arguments or parameters are described that would suggest data modification.
Attacks that exploit this kind of access
get_machine_config_pool_status. It is categorised as a Read tool in the Lumino MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Lumino MCP Server MCP server in PolicyLayer and add a rule for get_machine_config_pool_status: 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 Lumino MCP Server. Nothing to install.
get_machine_config_pool_status 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_machine_config_pool_status 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_machine_config_pool_status. 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_machine_config_pool_status is provided by the Lumino MCP Server MCP server (lumino-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 →