termf_nlp_alias · TermPipe MCP: Risk & Policy

WHAT IT DOES

What termf_nlp_alias does on TermPipe MCP

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

The tool generates shell aliases or functions and installs them into the shell environment. This constitutes executing/installing arbitrary shell code, as the installed alias/function can later run commands. The natural language input could be manipulated to install malicious shell functions. Given the terminal-access context of this server, misuse could have significant system-wide impact.

From the tool's definition 'Generate and install a shell alias/function from natural language' — this tool writes executable shell code (alias/function) into the shell environment, effectively executing/installing arbitrary shell commands derived from natural language input.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

termf_nlp_alias Rate-limited

termf_nlp_alias 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_nlp_alias": {
      "limits": [
        {
          "counter": "termf_nlp_alias_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_nlp_alias

What does the termf_nlp_alias tool do? +

Generate and install a shell alias/function from natural language. 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_nlp_alias? +

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

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

Can I rate-limit termf_nlp_alias? +

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

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

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