Create a new task in a project. tags must be existing tag IDs from the same project. Returns summary by default; set verbose=true for full data.
AI agents use create_task to create or update resources in Roadmap Skill — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Roadmap Skill environment.
The tool creates new data (a task) in a project management system and stores it locally. This is a Write operation because it creates/modifies data reversibly—tasks can be deleted or modified later. It does not execute arbitrary code, delete irreversibly, move money, or query only.
From the tool's definition Tool description states 'Create a new task in a project', which is a creation operation that modifies project state reversibly.
Documented attack patterns abuse exactly the kind of access create_task gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Roadmap Skill, and nothing reaches the server without passing your rules. This is the rule we recommend for create_task:
{
"version": "1",
"default": "deny",
"tools": {
"create_task": {
"limits": [
{
"counter": "create_task_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}create_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 new task in a project. tags must be existing tag IDs from the same project. Returns summary by default; set verbose=true for full data. It is categorised as a Write tool in the Roadmap Skill MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Roadmap Skill MCP server in PolicyLayer and add a rule for create_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 Roadmap Skill. Nothing to install.
create_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 create_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 create_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.
create_task is provided by the Roadmap Skill MCP server (shiquda/roadmap-skill). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 32 Roadmap Skill tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
32 Roadmap Skill tools catalogued and risk-classified — across an index of 42,500+ MCP servers.