kill_process · MCP MySQL Server MCP: Risk & Policy

WHAT IT DOES

What kill_process does on MCP MySQL Server

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

WHY IT NEEDS A POLICY

Why kill_process needs a policy

An AI agent can call kill_process faster than any human can review — one bad instruction and it creates or modifies resources in MCP MySQL Server by the hundred, each call as confident as the last.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

kill_process Rate-limited

kill_process 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": {
    "kill_process": {
      "limits": [
        {
          "counter": "kill_process_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 MCP MySQL Server, so you can run agents against it safely.

FAQ

Questions about kill_process

What does the kill_process tool do? +

Kill a MySQL process/connection by ID. It is categorised as a Write tool in the MCP MySQL 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 kill_process? +

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

What risk level is kill_process? +

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

Can I rate-limit kill_process? +

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

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

kill_process is provided by the MCP MySQL Server MCP server (kami2k1/mcp-mysql). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.