delete_log_destination

Delete a log destination

SERVERLinode MCP Server SOURCEtakashito/linode-mcp-server

Critical RISK CLASS

Category Destructive

Parameters 00 required

Recommended Hiddensee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/takashito-linode-mcp-server/delete-log-destination.md

WHAT IT DOES

What delete_log_destination does on Linode MCP Server

AI agents call delete_log_destination to permanently remove resources in Linode MCP Server, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

RISK

Why delete_log_destination is rated Critical

This tool permanently removes a log destination, which cannot be undone and results in loss of logging infrastructure or configuration. This qualifies as Destructive rather than Write because deletion is irreversible.

From the tool's definition Tool name explicitly contains 'delete'; description states 'Delete a log destination' indicating irreversible removal of logging configuration.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs delete_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 delete_log_destination, this is the rule to start with:

delete_log_destination Hidden

delete_log_destination is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "hide": [
    "delete_log_destination"
  ]
}

RESTRICT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Linode MCP Server, apply this rule, and every delete_log_destination call is checked against it from then on.

FAQ

Questions about delete_log_destination

What does the delete_log_destination tool do? +

Delete a log destination. It is categorised as a Destructive tool in the Linode MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on delete_log_destination? +

Register the Linode MCP Server MCP server in PolicyLayer and add a rule for delete_log_destination: 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 Linode MCP Server. Nothing to install.

What risk level is delete_log_destination? +

delete_log_destination is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit delete_log_destination? +

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

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

delete_log_destination is provided by the Linode MCP Server MCP server (takashito/linode-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Linode MCP Server, and thousands of servers like it.

This server

All 416 Linode MCP Server tools → Critical-risk tools on this server →

Across the catalogue

sms_delete_message on Twilio SMS MCP Server →delete_snapshot on Why Did You Render →calendar_delete_event on Templonix Lite MCP Server →delete_addon_domain on cPanel MCP Server → All critical-risk MCP tools → The MCP Attack Database →

Guides

Govern database agents →Blast radius →Tool call approval →