pod_install · Yaver MCP: Risk & Policy

WHAT IT DOES

What pod_install does on Yaver

AI agents use pod_install 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.

PARAMETERS

Parameter	Type	Required	Description
`directory`	string	—

Parameters from the server's own tool schema.

WHY IT NEEDS A POLICY

Why pod_install needs a policy

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

Risk signalsAccepts file system path (directory)

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

pod_install Rate-limited

pod_install 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": {
    "pod_install": {
      "limits": [
        {
          "counter": "pod_install_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Yaver, so you can run agents against it safely.

FAQ

Questions about pod_install

What does the pod_install tool do? +

Run pod install. 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.

What parameters does pod_install accept? +

pod_install accepts 1 parameter: directory. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on pod_install? +

Register the Yaver MCP server in PolicyLayer and add a rule for pod_install: 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.

What risk level is pod_install? +

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

Can I rate-limit pod_install? +

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

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

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