Displays high-level cluster state using
AI agents call pcs_cluster_status to retrieve information from Pacemaker MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and displays cluster state information without modifying, deleting, or executing arbitrary operations. It is a status/information retrieval function with no side effects, fitting the Read category. Severity is low because information disclosure about cluster status poses minimal risk even if accessed by an unauthorized agent.
From the tool's definition Tool name and context indicate 'pcs_cluster_status' retrieves cluster state via 'Displays high-level cluster state' (description truncated but clearly a query operation).
Attacks that exploit this kind of access
Displays high-level cluster state using. It is categorised as a Read tool in the Pacemaker MCP MCP Server, which means it retrieves data without modifying state.
Register the Pacemaker MCP server in PolicyLayer and add a rule for pcs_cluster_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 Pacemaker MCP. Nothing to install.
pcs_cluster_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 pcs_cluster_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 pcs_cluster_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.
pcs_cluster_status is provided by the Pacemaker MCP server (rishabhkodes/pacemaker-mcp). 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 →