termf_exec · TermPipe MCP: Risk & Policy

WHAT IT DOES

What termf_exec does on TermPipe MCP

AI agents invoke termf_exec 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 termf_exec needs a policy

This tool executes shell commands with effects determined entirely by the arguments passed. Shell command execution is inherently an Execute category risk because it can invoke any system operation (file deletion, network access, code compilation, credential theft, etc.). Severity is critical because an AI agent with access to arbitrary shell execution can cause extensive damage to systems, data, and infrastructure.

From the tool's definition Tool name 'termf_exec' and description 'Execute a shell command via TermPipe' directly indicate the tool runs arbitrary shell commands.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

termf_exec Rate-limited

termf_exec 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": {
    "termf_exec": {
      "limits": [
        {
          "counter": "termf_exec_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 termf_exec

What does the termf_exec tool do? +

Execute a shell command via TermPipe (existing method, preserved). 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 termf_exec? +

Register the TermPipe MCP server in PolicyLayer and add a rule for termf_exec: 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 termf_exec? +

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

Can I rate-limit termf_exec? +

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

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

termf_exec 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.