proxy_add
Add a reverse proxy route (e.g. myapp.local → localhost:3000).
This record as markdown: /tools/io-github-kivanccakmak-yaver/proxy-add.md
What proxy_add does on Yaver
AI agents use proxy_add to create or update resources in Yaver, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Yaver environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
tls | boolean | — | Enable HTTPS (default: true) |
domain | string | Yes | Local domain (e.g. myapp.local) |
target | string | Yes | Target (e.g. localhost:3000) |
Parameters from the server's own tool schema.
Why proxy_add is rated Medium
The tool creates or modifies proxy routing configuration, which is a Write operation—it adds a new route without deleting or executing arbitrary code. Severity is medium because misconfigured proxy routes could redirect traffic unexpectedly, but the effect is contained to local routing and reversible via proxy_remove or reconfiguration.
From the tool's definition Tool description states 'Add a reverse proxy route', which creates a new configuration entry (myapp.local → localhost:3000). This is a reversible modification to proxy settings.
Attacks that exploit this kind of access
The rule that runs proxy_add safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Yaver, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For proxy_add, this is the rule to start with:
proxy_add 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Yaver, apply this rule, and every proxy_add call is checked against it from then on.
Questions about proxy_add
Add a reverse proxy route (e.g. myapp.local → localhost:3000). It is categorised as a Write tool in the Yaver MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
proxy_add accepts 3 parameters: tls, domain, target. Required: domain, target. The full parameter table on this page comes from the server's own tool schema.
Register the Yaver MCP server in PolicyLayer and add a rule for proxy_add: 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 Yaver. Nothing to install.
proxy_add is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the proxy_add 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 proxy_add. 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.
proxy_add is provided by the Yaver MCP server (yaver-cli). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Yaver, and thousands of servers like it.
This server
Across the catalogue