pipedrive_create_task
Create a new task in a project. title and project_id are required. Use boolean is_done/is_milestone (same field names as the GET response); a milestone task must have a due_date. (Projects add-on; Projects API in public beta.)
This record as markdown: /tools/ckalima-pipedrive-mcp-server/pipedrive-create-task.md
What pipedrive_create_task does on Pipedrive MCP Server
AI agents use pipedrive_create_task to create or update resources in Pipedrive MCP Server, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Pipedrive MCP Server environment.
Why pipedrive_create_task is rated Medium
This tool creates new records (tasks) in Pipedrive, which is reversible (tasks can be deleted or modified). It does not execute arbitrary code, delete data irreversibly, move money, or read-only retrieve information. Creating tasks could impact business operations if an AI agent creates spam or unwanted tasks, but the blast radius is moderate since tasks can be easily removed.
From the tool's definition Tool description explicitly states 'Create a new task' which is a write operation. The tool accepts parameters like title, project_id, is_done, is_milestone, and due_date to create new data in the Pipedrive system.
Attacks that exploit this kind of access
The rule that runs pipedrive_create_task safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Pipedrive MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For pipedrive_create_task, this is the rule to start with:
pipedrive_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.
The button opens the PolicyLayer dashboard: create your workspace, connect Pipedrive MCP Server, apply this rule, and every pipedrive_create_task call is checked against it from then on.
Questions about pipedrive_create_task
Create a new task in a project. title and project_id are required. Use boolean is_done/is_milestone (same field names as the GET response); a milestone task must have a due_date. (Projects add-on; Projects API in public beta.). It is categorised as a Write tool in the Pipedrive MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Pipedrive MCP Server MCP server in PolicyLayer and add a rule for pipedrive_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 Pipedrive MCP Server. Nothing to install.
pipedrive_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 pipedrive_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 pipedrive_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.
pipedrive_create_task is provided by the Pipedrive MCP Server MCP server (ckalima/pipedrive-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Pipedrive MCP Server, and thousands of servers like it.
This server
Across the catalogue