Medium Risk

add_task_log

Add a log entry to track progress for a task

Part of the Sdd MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.

AI agents use add_task_log to create or modify resources in Sdd. Write operations carry medium risk because an autonomous agent could trigger bulk unintended modifications. Rate limits prevent a single agent session from making hundreds of changes in rapid succession. Argument validation ensures the agent passes expected values.

Without a policy, an AI agent could call add_task_log repeatedly, creating or modifying resources faster than any human could review. Intercept's rate limiting ensures write operations happen at a controlled pace, and argument validation catches malformed or unexpected inputs before they reach Sdd.

Write tools can modify data. A rate limit prevents runaway bulk operations from AI agents.

sdd.yaml
tools:
  add_task_log:
    rules:
      - action: allow
        rate_limit:
          max: 30
          window: 60

See the full Sdd policy for all 24 tools.

Tool Name add_task_log
Category Write
MCP Server Sdd MCP Server
Risk Level Medium

View all 24 tools →

Agents calling write-class tools like add_task_log have been implicated in these attack patterns. Read the full case and prevention policy for each:

Browse the full MCP Attack Database →

Other tools in the Write risk category across the catalogue. The same policy patterns (rate-limit, validate) apply to each.

What does the add_task_log tool do? +

Add a log entry to track progress for a task. It is categorised as a Write tool in the Sdd MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on add_task_log? +

Add a rule in your Intercept YAML policy under the tools section for add_task_log. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Sdd MCP server.

What risk level is add_task_log? +

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

Can I rate-limit add_task_log? +

Yes. Add a rate_limit block to the add_task_log rule in your Intercept 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 add_task_log completely? +

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

add_task_log is provided by the Sdd MCP server (@rafaelsouza-ai/mcp-server-sdd). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Let agents act without letting them run wild.

Deterministic policy on every MCP tool call. Per-identity grants. Full audit log.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.