create_task
AI agents use create_task to create or update resources in Procrastinator MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Procrastinator MCP Server environment.
Creating tasks is a reversible Write operation with no destructive or financial implications. Side effects are limited to adding data to a task management system. Severity is low as misuse (e.g., creating unwanted tasks) can be easily undone by deletion. Confidence is 0.85 rather than higher due to empty tool description, though the server context strongly supports the Write categorization.
From the tool's definition Tool name 'create_task' indicates task creation. Server description confirms it 'allow[s] users to...create...tasks through natural language commands.' Tool description is empty, limiting evidence specificity.
Attacks that exploit this kind of access
create_task. It is categorised as a Write tool in the Procrastinator MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Procrastinator 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 Procrastinator 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 Procrastinator MCP Server MCP server (mateusjunges/procrastinator-mcp-server). 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 →