vibecontrols_tunnels_add_agent_from_tunnel

Zero-config agent onboarding: probe a tunnel URL + API key, register + configure the agent in one shot.

SERVERVibecontrols SOURCE@vibecontrols/mcp

Medium RISK CLASS

Category Write

Parameters 62 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/vibecontrols-mcp/vibecontrols-tunnels-add-agent-from-tunnel.md

WHAT IT DOES

What vibecontrols_tunnels_add_agent_from_tunnel does on Vibecontrols

AI agents use vibecontrols_tunnels_add_agent_from_tunnel to create or update resources in Vibecontrols, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Vibecontrols environment.

Parameter	Type	Required
`name`	string	—
`apiKey`	string	Yes
`scopes`	array	—
`targetId`	string	—
`tunnelUrl`	string	Yes
`skipDevportalApp`	boolean	—

Parameters from the server's own tool schema.

RISK

Why vibecontrols_tunnels_add_agent_from_tunnel is rated Medium

An AI agent can call vibecontrols_tunnels_add_agent_from_tunnel faster than any human can review: one bad instruction and it creates or modifies resources in Vibecontrols by the hundred, each call as confident as the last.

Risk signalsHandles credentials or secrets (apiKey)

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs vibecontrols_tunnels_add_agent_from_tunnel safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Vibecontrols, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For vibecontrols_tunnels_add_agent_from_tunnel, this is the rule to start with:

vibecontrols_tunnels_add_agent_from_tunnel Rate-limited

vibecontrols_tunnels_add_agent_from_tunnel stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "vibecontrols_tunnels_add_agent_from_tunnel": {
      "limits": [
        {
          "counter": "vibecontrols_tunnels_add_agent_from_tunnel_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Vibecontrols, apply this rule, and every vibecontrols_tunnels_add_agent_from_tunnel call is checked against it from then on.

FAQ

Questions about vibecontrols_tunnels_add_agent_from_tunnel

What does the vibecontrols_tunnels_add_agent_from_tunnel tool do? +

Zero-config agent onboarding: probe a tunnel URL + API key, register + configure the agent in one shot. It is categorised as a Write tool in the Vibecontrols MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

What parameters does vibecontrols_tunnels_add_agent_from_tunnel accept? +

vibecontrols_tunnels_add_agent_from_tunnel accepts 6 parameters: name, apiKey, scopes, targetId, tunnelUrl, skipDevportalApp. Required: apiKey, tunnelUrl. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on vibecontrols_tunnels_add_agent_from_tunnel? +

Register the Vibecontrols MCP server in PolicyLayer and add a rule for vibecontrols_tunnels_add_agent_from_tunnel: 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 Vibecontrols. Nothing to install.

What risk level is vibecontrols_tunnels_add_agent_from_tunnel? +

vibecontrols_tunnels_add_agent_from_tunnel is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit vibecontrols_tunnels_add_agent_from_tunnel? +

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

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

vibecontrols_tunnels_add_agent_from_tunnel is provided by the Vibecontrols MCP server (@vibecontrols/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Vibecontrols, and thousands of servers like it.

This server

All 672 Vibecontrols tools →

Across the catalogue

add-tag on Kanban MCP Server →kb_add on Persistent Kb → The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →