ifp_send · TermPipe MCP: Risk & Policy

WHAT IT DOES

What ifp_send does on TermPipe MCP

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

This tool sends prompts to a local AI model (omniproxy running qwen2.5-coder-7b-instruct). In the context of a terminal access server that executes commands and manages files, sending prompts to a coding-focused LLM likely triggers code generation and/or execution. The server description emphasizes direct terminal access and command execution, making this an Execute-category tool.

From the tool's definition Send a prompt to local omniproxy (qwen2.5-coder-7b-instruct)

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

ifp_send Rate-limited

ifp_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": {
    "ifp_send": {
      "limits": [
        {
          "counter": "ifp_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 ifp_send

What does the ifp_send tool do? +

Send a prompt to local omniproxy (qwen2.5-coder-7b-instruct). 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 ifp_send? +

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

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

Can I rate-limit ifp_send? +

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

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

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