Medium Risk

update_setting

Update a setting value. Server settings (port, host, databasePath, logLevel, agentLivenessInterval, maxPortAttempts) are written to ~/.taskflow_config.json and require a restart. UI settings are saved to the local SQLite database.

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

@dalmasonto/taskflow-mcp Write Risk 2/5

AI agents use update_setting to create or modify resources in Taskflow. 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 update_setting 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 Taskflow.

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

taskflow.yaml
tools:
  update_setting:
    rules:
      - action: allow
        rate_limit:
          max: 30
          window: 60

See the full Taskflow policy for all 50 tools.

Tool Name update_setting
Category Write
MCP Server Taskflow MCP Server
Risk Level Medium

View all 50 tools →

Agents calling write-class tools like update_setting 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 update_setting tool do? +

Update a setting value. Server settings (port, host, databasePath, logLevel, agentLivenessInterval, maxPortAttempts) are written to ~/.taskflow_config.json and require a restart. UI settings are saved to the local SQLite database.. It is categorised as a Write tool in the Taskflow 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_setting? +

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

What risk level is update_setting? +

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

Can I rate-limit update_setting? +

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

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

update_setting is provided by the Taskflow MCP server (@dalmasonto/taskflow-mcp). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policies on Taskflow

Open source. One binary. Zero dependencies.

npx -y @policylayer/intercept
github.com/policylayer/intercept →
// GET IN TOUCH

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

Message sent.

We'll get back to you soon.