execute_terminal_state · WAKE Protocol MCP: Risk & Policy

WHAT IT DOES

What execute_terminal_state does on WAKE Protocol

AI agents invoke execute_terminal_state to trigger actions in WAKE Protocol. 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 execute_terminal_state needs a policy

execute_terminal_state triggers real processes with real consequences. An agent gone sideways doesn't fire it once — it starts dozens of builds, sends mass notifications, or burns through compute before anyone looks up.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

execute_terminal_state Rate-limited

execute_terminal_state 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": {
    "execute_terminal_state": {
      "limits": [
        {
          "counter": "execute_terminal_state_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 WAKE Protocol, so you can run agents against it safely.

FAQ

Questions about execute_terminal_state

What does the execute_terminal_state tool do? +

Execute terminal state (archive/distill/delete). Requires executor token. Only in EULOGY. It is categorised as a Execute tool in the WAKE Protocol MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on execute_terminal_state? +

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

What risk level is execute_terminal_state? +

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

Can I rate-limit execute_terminal_state? +

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

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

execute_terminal_state is provided by the WAKE Protocol MCP server (wake-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.