shared_storage_upsert · Yaver MCP: Risk & Policy

WHAT IT DOES

What shared_storage_upsert does on Yaver

AI agents use shared_storage_upsert 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
`profile`	string	Yes	JSON shared storage profile

Parameters from the server's own tool schema.

WHY IT NEEDS A POLICY

Why shared_storage_upsert needs a policy

An AI agent can call shared_storage_upsert 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.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

shared_storage_upsert Rate-limited

shared_storage_upsert 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": {
    "shared_storage_upsert": {
      "limits": [
        {
          "counter": "shared_storage_upsert_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 shared_storage_upsert

What does the shared_storage_upsert tool do? +

Create or update a shared storage profile. Profile is JSON with fields like {name,type,path|mount_path|endpoint,bucket,...}. 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 shared_storage_upsert accept? +

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

How do I enforce a policy on shared_storage_upsert? +

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

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

Can I rate-limit shared_storage_upsert? +

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

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

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