Batch create plan tasks for a lead.
AI agents use batchCreatePlanTasks to create or update resources in Lofty MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Lofty MCP Server environment.
This tool creates plan task records in a CRM system, which is a write operation that modifies data reversibly. The batch nature increases the potential blast radius (medium severity) if an agent mistakenly creates many tasks, but the operation remains reversible (tasks can be deleted).
From the tool's definition Tool name 'batchCreatePlanTasks' and description 'Batch create plan tasks for a lead' indicate creation of multiple records. The 'batch' prefix combined with 'create' shows this writes/creates data.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
Batch create plan tasks for a lead. It is categorised as a Write tool in the Lofty MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Lofty MCP Server MCP server in PolicyLayer and add a rule for batchCreatePlanTasks: 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 Lofty MCP Server. Nothing to install.
batchCreatePlanTasks 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 batchCreatePlanTasks 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 batchCreatePlanTasks. 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.
batchCreatePlanTasks is provided by the Lofty MCP Server MCP server (nerdsnipe-inc/lofty-mcp). 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 →