Execute NLP command via TermPipe. Translates natural language to CLI.
AI agents invoke termf_nlp 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.
This is an Execute-category tool with critical severity. It allows translation and execution of arbitrary CLI commands based on natural language input. The blast radius is critical because: (1) an AI agent receiving malicious or misinterpreted instructions could execute destructive commands (rm -rf, data exfiltration), (2) natural language translation introduces ambiguity and potential for unintended command…
From the tool's definition Tool description states 'Execute NLP command via TermPipe' and 'Translates natural language to CLI'. The server description emphasizes 'direct terminal access to execute commands'.
Attacks that exploit this kind of access
Execute NLP command via TermPipe. Translates natural language to CLI. 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.
Register the TermPipe MCP server in PolicyLayer and add a rule for termf_nlp: 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.
termf_nlp is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the termf_nlp 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.
Set action: deny in the PolicyLayer policy for termf_nlp. 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.
termf_nlp 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.
termf_nlp is one line of TermPipe's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →