update_log_destination

What update_log_destination does on Linode MCP Server

AI agents use update_log_destination to create or update resources in Linode MCP Server, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Linode MCP Server environment.

Why update_log_destination is rated Medium

Updating a log destination modifies existing system configuration, which is a reversible Write operation. The severity is medium because misconfiguration of log destinations could redirect sensitive logs to unintended locations, potentially exposing data or breaking monitoring/compliance systems. However, it remains reversible and does not irreversibly delete data or move financial assets.

From the tool's definition Tool name 'update_log_destination' indicates modification of an existing configuration. The verb 'update' is explicitly a Write action that modifies data reversibly. This affects logging infrastructure configuration rather than creating new resources.

The rule that runs update_log_destination safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Linode MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For update_log_destination, this is the rule to start with:

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

Questions about update_log_destination