maker_log_progress

Log a lesson-progress event for the session

SERVERCrow SOURCEkh0pper/crow

Medium RISK CLASS

Category Write

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/kh0pper-crow/maker-log-progress.md

WHAT IT DOES

What maker_log_progress does on Crow

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

RISK

Why maker_log_progress is rated Medium

This tool writes a new progress log entry for a session. It creates data (a lesson-progress event) but does not delete or overwrite existing data, execute code, or involve financial transactions. Misuse risk is low as it only records progress information.

From the tool's definition 'Log a lesson-progress event for the session' — creates/records a new progress event entry

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs maker_log_progress safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Crow, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For maker_log_progress, this is the rule to start with:

maker_log_progress Rate-limited

maker_log_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": {
    "maker_log_progress": {
      "limits": [
        {
          "counter": "maker_log_progress_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Crow, apply this rule, and every maker_log_progress call is checked against it from then on.

FAQ

Questions about maker_log_progress

What does the maker_log_progress tool do? +

Log a lesson-progress event for the session. It is categorised as a Write tool in the Crow MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on maker_log_progress? +

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

What risk level is maker_log_progress? +

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

Can I rate-limit maker_log_progress? +

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

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

maker_log_progress is provided by the Crow MCP server (kh0pper/crow). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Crow, and thousands of servers like it.

This server

All 587 Crow tools →

Across the catalogue

The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →