smart_replace
AI agents invoke smart_replace 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.
The server context is high-risk — it provides direct terminal access and file management. 'smart_replace' likely performs file content replacement (a Write or potentially Destructive operation), but without a description, this cannot be confirmed. Given sibling tools like 'append_file' and the server's file management capabilities, this tool most plausibly modifies file content.
From the tool's definition Tool name 'smart_replace' on a server that provides 'direct terminal access to execute commands, manage files, and run persistent REPL sessions'. The tool description is empty and uninformative.
Attacks that exploit this kind of access
smart_replace. 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 smart_replace: 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.
smart_replace 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 smart_replace 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 smart_replace. 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.
smart_replace 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.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →