set_task_start_date · RTM MCP Server MCP: Risk & Policy

WHAT IT DOES

What set_task_start_date does on RTM MCP Server

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

WHY IT NEEDS A POLICY

Why set_task_start_date needs a policy

Setting a task's start date modifies task data in a reversible manner (the date can be changed again). This is a Write operation rather than Read (it changes state), Execute (it doesn't run arbitrary code), or Destructive (changes are undoable). Severity is medium due to potential task scheduling disruptions if misused by an agent, but impact is limited to metadata modification without cascading effects.

From the tool's definition Tool name 'set_task_start_date' indicates modification of task metadata. Server description states 'full API coverage for task manipulation' and lists sibling tools including 'add_task', 'complete_task', and 'delete_task' which establish this as a task…

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

set_task_start_date Rate-limited

set_task_start_date 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": {
    "set_task_start_date": {
      "limits": [
        {
          "counter": "set_task_start_date_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 RTM MCP Server, so you can run agents against it safely.

FAQ

Questions about set_task_start_date

What does the set_task_start_date tool do? +

set_task_start_date. It is categorised as a Write tool in the RTM 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 set_task_start_date? +

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

What risk level is set_task_start_date? +

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

Can I rate-limit set_task_start_date? +

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

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

set_task_start_date is provided by the RTM MCP Server MCP server (ljadach/rtm-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.