AI agents use workspaceCreateProject to create or update resources in Mcp Taskade — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Mcp Taskade environment.
The tool creates a new project, which is a write operation—it adds data to the system. It is not destructive (creation is reversible), not financial, and not code execution. Severity is medium because creating a project could consume resources, affect workspace organization, or be misused to create many dummy projects, but the impact is scoped to workspace data and reversible.
From the tool's definition Tool name 'workspaceCreateProject' and description 'Create a project in a workspace' indicate creation of a new data object (project) in a workspace. This is reversible (project can typically be deleted later).
Documented attack patterns abuse exactly the kind of access workspaceCreateProject gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Mcp Taskade, and nothing reaches the server without passing your rules. This is the rule we recommend for workspaceCreateProject:
{
"version": "1",
"default": "deny",
"tools": {
"workspaceCreateProject": {
"limits": [
{
"counter": "workspacecreateproject_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}workspaceCreateProject 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 project in a workspace. It is categorised as a Write tool in the Mcp Taskade MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Mcp Taskade MCP server in PolicyLayer and add a rule for workspaceCreateProject: 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 Mcp Taskade. Nothing to install.
workspaceCreateProject 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 workspaceCreateProject 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 workspaceCreateProject. 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.
workspaceCreateProject is provided by the Mcp Taskade MCP server (taskade/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 57 Mcp Taskade tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
57 Mcp Taskade tools catalogued and risk-classified — across an index of 42,500+ MCP servers.