record_audit_progress · Slopweaver MCP: Risk & Policy

WHAT IT DOES

What record_audit_progress does on Slopweaver

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

WHY IT NEEDS A POLICY

Why record_audit_progress needs a policy

This tool writes (appends) progress event records to a local log file. It is a reversible write operation — appending to a log file does not delete or overwrite existing data. The blast radius is low since it only affects a local audit progress log file, and misuse would at worst produce spurious log entries.

From the tool's definition Append one progress event to the per-audit JSONL log... Uses O_APPEND for race-free concurrent appends

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

record_audit_progress Rate-limited

record_audit_progress 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_audit_progress": {
      "limits": [
        {
          "counter": "record_audit_progress_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 Slopweaver, so you can run agents against it safely.

FAQ

Questions about record_audit_progress

What does the record_audit_progress tool do? +

Append one progress event to the per-audit JSONL log at <data-dir>/audit-progress/<audit_id>.jsonl. Call from inside a mega-audit run for each phase transition so the live UI can tail the file. Uses O_APPEND for race-free concurrent appends; the per-audit_id layout means concurrent audits never contend on the same file. It is categorised as a Write tool in the Slopweaver 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_audit_progress? +

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

What risk level is record_audit_progress? +

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

Can I rate-limit record_audit_progress? +

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

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

record_audit_progress is provided by the Slopweaver MCP server (slopweaver/slopweaver). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.