createTaskV1

Create a task (v1 API). Type: Other | Call | Email | Text. AssignedRole: Agent | Assistant.

Server Lofty MCP Server nerdsnipe-inc/lofty-mcp
Category Write
Risk class Medium
Parameters 00 required

What createTaskV1 does on Lofty MCP Server

AI agents use createTaskV1 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.

Why createTaskV1 needs a policy

Creating tasks in a CRM system modifies data by adding new records, making this a Write operation rather than Read (which would only retrieve data). It is not Destructive because task creation is reversible (tasks can be deleted or modified later). It is not Execute because it does not run arbitrary code or shell commands—it performs a specific, bounded API operation.

From the tool's definition Tool description explicitly states it 'Create[s] a task', which is a reversible data creation operation. The tool accepts parameters (Type and AssignedRole) that determine what task is created and who it's assigned to, modifying the CRM state.

Questions about createTaskV1

What does the createTaskV1 tool do? +

Create a task (v1 API). Type: Other | Call | Email | Text. AssignedRole: Agent | Assistant. 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.

How do I enforce a policy on createTaskV1? +

Register the Lofty MCP Server MCP server in PolicyLayer and add a rule for createTaskV1: 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.

What risk level is createTaskV1? +

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

Can I rate-limit createTaskV1? +

Yes. Add a rate_limit block to the createTaskV1 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 createTaskV1 completely? +

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

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

// LOOK UP ANOTHER 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 →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.