Medium Risk

add_task

Create a new task. ${departmentRequired ?

How to control add_task ↓

What add_task does on Writbase

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

Medium Risk

Why add_task needs a policy

This tool creates new task records in a task management system. Creation of data is a Write operation. Severity is medium because task creation in a multi-agent fleet system could enable an attacker to create malicious tasks for agents to execute, potentially leading to unintended operations, but the impact is limited by scoped permissions mentioned in the server description.

From the tool's definition Tool name 'add_task' and description 'Create a new task' indicate creation of new data records.

Documented attack patterns abuse exactly the kind of access add_task gives an agent:

How to control add_task

PolicyLayer is an MCP gateway — it sits between your AI agents and Writbase, and nothing reaches the server without passing your rules. This is the rule we recommend for add_task:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "add_task": {
      "limits": [
        {
          "counter": "add_task_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

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

  1. Create a free account and register Writbase — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
LIMIT THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about add_task

What does the add_task tool do? +

Create a new task. ${departmentRequired ?. It is categorised as a Write tool in the Writbase 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? +

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

What risk level is add_task? +

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

Can I rate-limit add_task? +

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

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

add_task is provided by the Writbase MCP server (https://{PROJECT_REF}.supabase.co/functions/v1/mcp-server/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Writbase tool call.

Start from Writbase, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

Free to start. No card required.

13 Writbase tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.