新しいタスクを作成します。サブタスクも定義できます。
AI agents use create_task to create or update resources in TaskMateAI — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your TaskMateAI environment.
This tool creates new data entries (tasks and subtasks) in a task management system. Creation is reversible (tasks can be deleted or marked incomplete), making it Write rather than Destructive. The severity is medium because an AI agent could create numerous unwanted tasks, disrupt workflow organization, or fill the system with spam tasks, but the impact is containable and reversible.
From the tool's definition Tool name 'create_task' and description stating it creates new tasks (新しいタスクを作成します means 'creates new tasks'). Can also define subtasks, indicating data creation capability.
Attacks that exploit this kind of access
新しいタスクを作成します。サブタスクも定義できます。. It is categorised as a Write tool in the TaskMateAI MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the TaskMateAI 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 TaskMateAI. 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 TaskMateAI MCP server (newaitees/taskmateai). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →