set_coredump_enabled · systemd-coredump MCP Server MCP

WHAT IT DOES

What set_coredump_enabled does on systemd-coredump MCP Server

AI agents invoke set_coredump_enabled to trigger actions in systemd-coredump MCP Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.

WHY IT NEEDS A POLICY

Why set_coredump_enabled needs a policy

This tool modifies an active system setting (enabling/disabling core dump generation), which is an external system operation beyond simple data write. Disabling core dumps could hinder incident response and forensic analysis; enabling them could expose sensitive memory contents.

From the tool's definition 'Enable or disable core dump generation' — this triggers a system-level configuration change that controls whether core dumps are generated, affecting system behavior and potentially security posture

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

set_coredump_enabled Rate-limited

set_coredump_enabled stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "set_coredump_enabled": {
      "limits": [
        {
          "counter": "set_coredump_enabled_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

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

FAQ

Questions about set_coredump_enabled

What does the set_coredump_enabled tool do? +

Enable or disable core dump generation. It is categorised as a Execute tool in the systemd-coredump MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on set_coredump_enabled? +

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

What risk level is set_coredump_enabled? +

set_coredump_enabled is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit set_coredump_enabled? +

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

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

set_coredump_enabled is provided by the systemd-coredump MCP Server MCP server (signal-slot/mcp-systemd-coredump). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.