record_task_event · Agent Bus MCP: Risk & Policy

WHAT IT DOES

What record_task_event does on Agent Bus

AI agents use record_task_event 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_task_event needs a policy

This tool writes/appends log entries to a task event log. It creates new data (log rows) but does not delete, execute code, or involve financial transactions. The blast radius is low since it only adds progress/event metadata to an existing task record.

From the tool's definition Append a task progress/event log row. Use for phases, progress notes, command summaries, result notes, and cancellation context.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

record_task_event Rate-limited

record_task_event 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_task_event": {
      "limits": [
        {
          "counter": "record_task_event_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_task_event

What does the record_task_event tool do? +

Append a task progress/event log row. Use for phases, progress notes, command summaries, result notes, and cancellation context. 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_task_event? +

Register the Agent Bus MCP server in PolicyLayer and add a rule for record_task_event: 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_task_event? +

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

Can I rate-limit record_task_event? +

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

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

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