record_test_result · Agent Bus MCP: Risk & Policy

WHAT IT DOES

What record_test_result does on Agent Bus

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

WHY IT NEEDS A POLICY

Why record_test_result needs a policy

This tool writes/stores test result data (test/build/lint evidence) to a report. It creates or modifies data reversibly with no destructive, financial, or execution side effects. Severity is low as it only records metadata about test outcomes.

From the tool's definition Record explicit test/build/lint evidence for final_report

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

record_test_result Rate-limited

record_test_result 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": {
    "record_test_result": {
      "limits": [
        {
          "counter": "record_test_result_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 Agent Bus, so you can run agents against it safely.

FAQ

Questions about record_test_result

What does the record_test_result tool do? +

Record explicit test/build/lint evidence for final_report. It is categorised as a Write tool in the Agent Bus MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on record_test_result? +

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

What risk level is record_test_result? +

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

Can I rate-limit record_test_result? +

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

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

record_test_result is provided by the Agent Bus MCP server (mustaphasteph/agent-bus). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.