save_test_record · Yo Bug MCP: Risk & Policy

WHAT IT DOES

What save_test_record does on Yo Bug

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

WHY IT NEEDS A POLICY

Why save_test_record needs a policy

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

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

save_test_record Rate-limited

save_test_record 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": {
    "save_test_record": {
      "limits": [
        {
          "counter": "save_test_record_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 Yo Bug, so you can run agents against it safely.

FAQ

Questions about save_test_record

What does the save_test_record tool do? +

Save test results for a module. Call after checklist testing is complete to accumulate test history. This data is used by get_test_history to identify frequently failing scenarios. It is categorised as a Write tool in the Yo Bug MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on save_test_record? +

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

What risk level is save_test_record? +

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

Can I rate-limit save_test_record? +

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

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

save_test_record is provided by the Yo Bug MCP server (wyykerwin/yo-bug). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.