set_task_name · RTM MCP Server MCP: Risk & Policy

WHAT IT DOES

What set_task_name does on RTM MCP Server

AI agents use set_task_name 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_name needs a policy

Renaming a task is a write operation—it modifies data reversibly and can be undone (the original name can be restored). It does not execute external code, delete data irreversibly, or move money. The severity is medium because misuse could corrupt task organization or confuse workflows, but the impact is limited to task metadata and can be corrected.

From the tool's definition Tool name 'set_task_name' and description 'Rename a task' indicates modifying existing task data. This is a reversible change operation that updates task metadata without destroying data.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

set_task_name Rate-limited

set_task_name 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_name": {
      "limits": [
        {
          "counter": "set_task_name_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_name

What does the set_task_name tool do? +

Rename a task. 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_name? +

Register the RTM MCP Server MCP server in PolicyLayer and add a rule for set_task_name: 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_name? +

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

Can I rate-limit set_task_name? +

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

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

set_task_name 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.