log_progress · Agent Progress Tracker MCP Server MCP

WHAT IT DOES

What log_progress does on Agent Progress Tracker MCP Server

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

WHY IT NEEDS A POLICY

Why log_progress needs a policy

This tool creates new records in a database (write operation). It does not delete or overwrite existing data, execute code, or involve financial transactions. Misuse could result in polluted or misleading progress logs affecting multi-agent workflows, hence medium severity.

From the tool's definition 'Log completed work with title, content, and optional tags' and 'Returns entry ID for future reference' — creates new entries in persistent SQLite storage

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

log_progress Rate-limited

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": {
    "log_progress": {
      "limits": [
        {
          "counter": "log_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 Agent Progress Tracker MCP Server, so you can run agents against it safely.

FAQ

Questions about log_progress

What does the log_progress tool do? +

Log completed work with title, content, and optional tags. Use after finishing significant tasks, decisions, or milestones. Returns entry ID for future reference. It is categorised as a Write tool in the Agent Progress Tracker MCP Server 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_progress? +

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

What risk level is log_progress? +

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

Can I rate-limit log_progress? +

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

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

log_progress is provided by the Agent Progress Tracker MCP Server MCP server (thesammykins/context-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.