Create a new organization. Auto-backed up.
AI agents use create_organization to create or update resources in Mcp Pipedrive — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Mcp Pipedrive environment.
This tool creates (writes) new data to the CRM system. It is categorized as Write rather than Read because it modifies the database by adding a new entity. It is not Destructive because organizations can be deleted or the action reversed. It is not Execute because it doesn't run arbitrary code or commands.
From the tool's definition Tool creates a new organization record in Pipedrive. Description states 'Create a new organization' and mentions 'Auto-backed up', indicating reversibility via backup/restore capabilities mentioned in server description.
Attacks that exploit this kind of access
Create a new organization. Auto-backed up. It is categorised as a Write tool in the Mcp Pipedrive MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Mcp Pipedrive MCP server in PolicyLayer and add a rule for create_organization: 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 Mcp Pipedrive. Nothing to install.
create_organization 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_organization 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_organization. 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_organization is provided by the Mcp Pipedrive MCP server (leonardoceron-yvy/yvy-mcp-pipedrive). 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 →