cond_daemon_send · TermPipe MCP: Risk & Policy

WHAT IT DOES

What cond_daemon_send does on TermPipe MCP

AI agents invoke cond_daemon_send to trigger actions in TermPipe MCP. 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 cond_daemon_send needs a policy

The server description explicitly provides terminal access and command execution. The 'daemon_send' naming pattern strongly implies sending commands or signals to a background daemon process, which is an Execute-category action. However, the empty description prevents certainty about exact behavior, so confidence is reduced.

From the tool's definition Tool name 'cond_daemon_send' on a server that 'provides AI assistants with direct terminal access to execute commands'; sibling tools include terminal/REPL operations

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

cond_daemon_send Rate-limited

cond_daemon_send 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": {
    "cond_daemon_send": {
      "limits": [
        {
          "counter": "cond_daemon_send_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 TermPipe MCP, so you can run agents against it safely.

FAQ

Questions about cond_daemon_send

What does the cond_daemon_send tool do? +

cond_daemon_send. It is categorised as a Execute tool in the TermPipe MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on cond_daemon_send? +

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

What risk level is cond_daemon_send? +

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

Can I rate-limit cond_daemon_send? +

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

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

cond_daemon_send is provided by the TermPipe MCP server (wbind-core/termpipe-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.