Create a task in a department where you have assign permission. Use this to create work in another team
AI agents use assign_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.
assign_task creates new task records within a department, which is a reversible write operation. It modifies system state by adding data but does not execute arbitrary code, delete records, or move money. The 'scoped permissions' design mitigates some risk, but an agent with inappropriate department access could create spurious or malicious work assignments affecting team workflows.
From the tool's definition Tool description states 'Create a task in a department' and the sibling tools include task management operations like add_task, get_tasks, and manage_permissions, indicating this is a data-creation function within a scoped permission system.
Documented attack patterns abuse exactly the kind of access assign_task gives an agent:
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 assign_task:
{
"version": "1",
"default": "deny",
"tools": {
"assign_task": {
"limits": [
{
"counter": "assign_task_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}assign_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.
Free to start. No card required.
Create a task in a department where you have assign permission. Use this to create work in another team. 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.
Register the Writbase MCP server in PolicyLayer and add a rule for assign_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.
assign_task is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the assign_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.
Set action: deny in the PolicyLayer policy for assign_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.
assign_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.
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.