update_scale_threshold
AI agents use update_scale_threshold to create or update resources in Morpheus MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Morpheus MCP Server environment.
The tool modifies scaling thresholds for cloud infrastructure, which affects auto-scaling behavior and resource allocation policies. This is a Write operation (reversible configuration change) rather than Execute or Destructive. Severity is high because misconfiguration could cause unintended resource scaling, cost overruns, or service disruptions across multi-tenant environments.
From the tool's definition Tool name 'update_scale_threshold' indicates modification of scaling configuration. Server context shows it operates on HPE Morpheus cloud infrastructure management, enabling resource provisioning and administrative tasks.
Attacks that exploit this kind of access
update_scale_threshold. It is categorised as a Write tool in the Morpheus MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Morpheus MCP Server MCP server in PolicyLayer and add a rule for update_scale_threshold: 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.
update_scale_threshold is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the update_scale_threshold 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 update_scale_threshold. 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.
update_scale_threshold 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 →