mock_add · Yaver MCP: Risk & Policy

WHAT IT DOES

What mock_add does on Yaver

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

PARAMETERS

Parameter	Type	Required	Description
`body`	string	Yes	Response body (JSON)
`path`	string	Yes	URL path
`method`	string	Yes	HTTP method
`status`	integer	Yes	Response status code
`headers`	object	—	Response headers

Parameters from the server's own tool schema.

WHY IT NEEDS A POLICY

Why mock_add needs a policy

An AI agent can call mock_add 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 (path) · Accepts raw HTML/template content (body)

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

mock_add Rate-limited

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

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "mock_add": {
      "limits": [
        {
          "counter": "mock_add_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 mock_add

What does the mock_add tool do? +

Add a mock route. 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 mock_add accept? +

mock_add accepts 5 parameters: body, path, method, status, headers. Required: body, path, method, status. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on mock_add? +

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

What risk level is mock_add? +

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

Can I rate-limit mock_add? +

Yes. Add a rate_limit block to the mock_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.

How do I block mock_add completely? +

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

What MCP server provides mock_add? +

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