log_task · Productivity Tracker MCP Server MCP

WHAT IT DOES

What log_task does on Productivity Tracker MCP Server

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

WHY IT NEEDS A POLICY

Why log_task needs a policy

This tool creates a new entry in the database, which is a reversible write operation. It does not delete, execute code, or involve financial transactions. Misuse could result in polluted task data, but the blast radius is low since records can be removed or corrected.

From the tool's definition "Log a new task with category and status" — creates a new task record in the local SQLite database

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

log_task Rate-limited

log_task 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_task": {
      "limits": [
        {
          "counter": "log_task_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 Productivity Tracker MCP Server, so you can run agents against it safely.

FAQ

Questions about log_task

What does the log_task tool do? +

Log a new task with category and status. It is categorised as a Write tool in the Productivity 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_task? +

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

What risk level is log_task? +

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

Can I rate-limit log_task? +

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

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

log_task is provided by the Productivity Tracker MCP Server MCP server (manasamadgul/tracker). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.