List auto-scaling threshold rules — CPU and memory triggers for scale-up/down.
AI agents call list_scale_thresholds to retrieve information from Morpheus MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and displays existing auto-scaling threshold configurations (CPU and memory triggers). It performs no modifications, deletions, code execution, or financial transactions. It is purely informational, reading static configuration data from the Morpheus infrastructure management system. The blast radius of misuse is minimal — an AI agent retrieving this information cannot cause harm.
From the tool's definition Tool description explicitly states 'List auto-scaling threshold rules' — a read operation that retrieves configuration data without modifying or executing anything.
Attacks that exploit this kind of access
List auto-scaling threshold rules — CPU and memory triggers for scale-up/down. It is categorised as a Read tool in the Morpheus MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Morpheus MCP Server MCP server in PolicyLayer and add a rule for list_scale_thresholds: 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 Morpheus MCP Server. Nothing to install.
list_scale_thresholds 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 list_scale_thresholds 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 list_scale_thresholds. 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.
list_scale_thresholds is provided by the Morpheus MCP Server MCP server (nixndme/morpheus-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 →