ploomes_tasks_create · Ploomes MCP: Risk & Policy

WHAT IT DOES

What ploomes_tasks_create does on Ploomes

AI agents use ploomes_tasks_create to create or update resources in Ploomes — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Ploomes environment.

WHY IT NEEDS A POLICY

Why ploomes_tasks_create needs a policy

The tool creates new data (a task) in the CRM system, which is a reversible write operation. It does not execute arbitrary code, delete data irreversibly, or move money. The severity is medium because task creation in a CRM could affect business workflows and decision-making, but the impact is limited to a single task record and the operation is reversible (tasks can be deleted or modified later).

From the tool's definition Tool name includes 'create' and description states 'Create a new task in Ploomes CRM.' This is a data creation operation that modifies CRM state by adding a new task record.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

ploomes_tasks_create Rate-limited

ploomes_tasks_create 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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "ploomes_tasks_create": {
      "limits": [
        {
          "counter": "ploomes_tasks_create_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Ploomes, so you can run agents against it safely.

FAQ

Questions about ploomes_tasks_create

What does the ploomes_tasks_create tool do? +

Create a new task in Ploomes CRM. Attach to a deal via DealId or to a contact via ContactId. It is categorised as a Write tool in the Ploomes MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on ploomes_tasks_create? +

Register the Ploomes MCP server in PolicyLayer and add a rule for ploomes_tasks_create: 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 Ploomes. Nothing to install.

What risk level is ploomes_tasks_create? +

ploomes_tasks_create is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit ploomes_tasks_create? +

Yes. Add a rate_limit block to the ploomes_tasks_create 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.

How do I block ploomes_tasks_create completely? +

Set action: deny in the PolicyLayer policy for ploomes_tasks_create. 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.

What MCP server provides ploomes_tasks_create? +

ploomes_tasks_create is provided by the Ploomes MCP server (ploomes-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.