AI agents use create_task to create or update resources in LunaTask MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your LunaTask MCP Server environment.
The tool creates new task data in LunaTask, a productivity management system. This is a reversible write operation—tasks can be modified or deleted. The severity is medium because misuse could generate unwanted task clutter or scheduling conflicts, but the impact is contained within a personal productivity system and reversible via delete_task.
From the tool's definition Tool name 'create_task' with context indicating LunaTask API for managing tasks. Sibling tools include create_journal_entry, create_note, create_person, and update_note, establishing a pattern of Create/Write operations.
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 LunaTask MCP Server, 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_task. It is categorised as a Write tool in the LunaTask MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the LunaTask MCP Server 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 LunaTask MCP Server. 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 LunaTask MCP Server MCP server (tensorfreitas/lunatask-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from LunaTask MCP Server, 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.
12 LunaTask MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.