log_append · Lockstep MCP: Risk & Policy

WHAT IT DOES

What log_append does on Lockstep

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

WHY IT NEEDS A POLICY

Why log_append needs a policy

This tool creates or modifies log data by appending entries. It is reversible (logs can be corrected or purged), so it does not qualify as Destructive. In a multi-agent coordination context, appending to logs could affect audit trails and agent decision-making, raising the severity to medium due to potential downstream impacts on project coordination and debugging.

From the tool's definition Tool name 'log_append' and description 'Append a log entry' indicate creation/modification of log data. The verb 'append' is a write operation that adds new records to a log in a reversible manner (logs can be edited or cleared).

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

log_append Rate-limited

log_append 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": {
    "log_append": {
      "limits": [
        {
          "counter": "log_append_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 Lockstep, so you can run agents against it safely.

FAQ

Questions about log_append

What does the log_append tool do? +

Append a log entry. It is categorised as a Write tool in the Lockstep MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on log_append? +

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

What risk level is log_append? +

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

Can I rate-limit log_append? +

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

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

log_append is provided by the Lockstep MCP server (tmmoore286/lockstep-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.