Create, rename, or archive departments. Manager only.
AI agents use manage_departments 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.
This tool modifies organizational structure by creating new departments, renaming existing ones, or archiving them. These are all write operations that can be reversed by a manager. While archiving might seem destructive, the description uses 'archive' rather than 'delete' or 'purge', indicating reversibility.
From the tool's definition Tool description states 'Create, rename, or archive departments.' Create and rename are reversible write operations; archive is also reversible (implied by 'Manager only' access control suggesting governance rather than destruction).
Documented attack patterns abuse exactly the kind of access manage_departments 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 manage_departments:
{
"version": "1",
"default": "deny",
"tools": {
"manage_departments": {
"limits": [
{
"counter": "manage_departments_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}manage_departments 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, rename, or archive departments. Manager only. 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 manage_departments: 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.
manage_departments 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 manage_departments 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 manage_departments. 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.
manage_departments 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.