update_settings · TodoPomo MCP Server MCP: Risk & Policy

WHAT IT DOES

What update_settings does on TodoPomo MCP Server

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

WHY IT NEEDS A POLICY

Why update_settings needs a policy

This tool modifies settings (a form of data) but the changes are non-destructive and reversible. It does not execute arbitrary code, delete data, or trigger external operations. It falls squarely in the Write category. Severity is low because misconfigured timer settings have minimal blast radius—worst case, a user has suboptimal Pomodoro intervals, which causes no data loss or external harm.

From the tool's definition Tool name 'update_settings' and description 'Update pomodoro timer settings' indicate modification of configuration data. The action is reversible—settings can be changed again.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

update_settings Rate-limited

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

FAQ

Questions about update_settings

What does the update_settings tool do? +

Update pomodoro timer settings. It is categorised as a Write tool in the TodoPomo 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 update_settings? +

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

What risk level is update_settings? +

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

Can I rate-limit update_settings? +

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

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

update_settings is provided by the TodoPomo MCP Server MCP server (pratyayrajak/todopomo-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.