update_log_settings · Morpheus MCP Server MCP: Risk & Policy

WHAT IT DOES

What update_log_settings does on Morpheus MCP Server

AI agents use update_log_settings 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.

WHY IT NEEDS A POLICY

Why update_log_settings needs a policy

This tool modifies logging configuration in an HPE Morpheus appliance, which affects audit trails, monitoring, and compliance posture. While reversible (category Write, not Destructive), misconfiguration could disable critical logging, hide malicious activity, or impact incident investigation.

From the tool's definition Tool name 'update_log_settings' and description 'Update Morpheus logging configuration' indicate modification of system configuration settings. The verb 'update' confirms reversible write operation.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

update_log_settings Rate-limited

update_log_settings stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "update_log_settings": {
      "limits": [
        {
          "counter": "update_log_settings_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Morpheus MCP Server, so you can run agents against it safely.

FAQ

Questions about update_log_settings

What does the update_log_settings tool do? +

Update Morpheus logging configuration. 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.

How do I enforce a policy on update_log_settings? +

Register the Morpheus MCP Server MCP server in PolicyLayer and add a rule for update_log_settings: 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.

What risk level is update_log_settings? +

update_log_settings is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit update_log_settings? +

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

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

update_log_settings 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.