// SCAN REPORT

systemd-coredump MCP Server

6 tools. 2 can modify or destroy data without limits.

2 write tools that can modify data. Rate limits recommended.

Last updated: 30 Jun 2026

2 can modify or destroy data

4 read-only

6 tools total

Community server · catalogue entry verified 30/06/2026

How to control systemd-coredump MCP Server ↓

TOOL MAP

What systemd-coredump MCP Server exposes to your agents

Read (4) Write / Execute (2) Destructive / Financial (0)

Running more than one server? Check your whole stack →

MOST DANGEROUS TOOLS

High Risk

The most dangerous systemd-coredump MCP Server tools

Execute · High set_coredump_enabled This tool modifies an active system setting (enabling/disabling core dump generation), which is an external system operation beyond simple data write. Write · Medium extract_coredump This tool writes/exports a core dump to a file on the filesystem.

2 of systemd-coredump MCP Server's 6 tools can modify, destroy, or commit something on every call — and an agent calls them with no built-in limits.

POLICY

How to control systemd-coredump MCP Server

PolicyLayer is an MCP gateway — it sits between your AI agents and systemd-coredump MCP Server, and nothing reaches the server without passing your rules. These are the rules we recommend:

Rate limit write operations

{
  "extract_coredump": {
    "limits": [
      {
        "counter": "extract_coredump_per_hour",
        "window": "hour",
        "max": 30,
        "scope": "grant"
      }
    ]
  }
}

Prevents bulk unintended modifications from agents caught in loops.

Cap read operations

{
  "get_coredump_config": {
    "limits": [
      {
        "counter": "get_coredump_config_per_minute",
        "window": "minute",
        "max": 60,
        "scope": "grant"
      }
    ]
  }
}

Controls API costs and prevents retry loops from exhausting upstream rate limits.

Create a free account and register systemd-coredump MCP Server — nothing to install.
Add these rules — paste them, or build them visually. Tune the limits to your setup.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

ENFORCE POLICY ON SYSTEMD-COREDUMP →

Instant setup, no code required.

FULL CATALOGUE

All 6 systemd-coredump MCP Server tools

EXECUTE 1 tools

Execute set_coredump_enabled Enable or disable core dump generation

WRITE 1 tools

Write extract_coredump Extract a coredump to a file

READ 4 tools

Read get_coredump_config Get the current core dump configuration of the system Read get_coredump_info Get detailed information about a specific coredump Read get_stacktrace Get stack trace from a coredump using GDB Read list_coredumps List available coredumps in the system

FAQ

Questions about systemd-coredump MCP Server

How do I prevent bulk modifications through systemd-coredump MCP Server? +

The systemd-coredump MCP Server server has 1 write tools including extract_coredump. Set a rate limit in your policy -- for example, 10 calls per hour prevents an agent from making more than 10 modifications per hour. PolicyLayer enforces this at the gateway, before calls reach systemd-coredump MCP Server.

How many tools does the systemd-coredump MCP Server MCP server expose? +

6 tools across 2 categories: Read, Write. 4 are read-only. 2 can modify, create, or delete data.

How do I enforce a policy on systemd-coredump MCP Server? +

Register the systemd-coredump MCP Server MCP server in PolicyLayer, apply the suggested rules above (adjust the limits to your use case), and point your AI client at the PolicyLayer proxy URL instead of the server directly. Your agents keep the same tools; PolicyLayer evaluates every call against policy before it executes. Nothing to install, live in minutes.

Enforce policy on every systemd-coredump MCP Server tool call.

Deterministic rules across all 6 systemd-coredump MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

ENFORCE POLICY ON SYSTEMD-COREDUMP →

Instant setup, no code required.

6 systemd-coredump MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.