Create a new batch of items
AI agents use create_batch to create or update resources in ConsignCloud MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your ConsignCloud MCP Server environment.
This is a Write operation as it creates new business records (batch of items) with reversible side effects. The blast radius is medium because creating batches could impact inventory tracking and sales records, but the operation is reversible through deletion or correction. It does not execute arbitrary code, destroy data irreversibly, or move money.
From the tool's definition Tool name 'create_batch' and description 'Create a new batch of items' indicate the tool creates new data (batch records) within the consignment/retail system.
Attacks that exploit this kind of access
Create a new batch of items. It is categorised as a Write tool in the ConsignCloud MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the ConsignCloud MCP Server MCP server in PolicyLayer and add a rule for create_batch: 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 ConsignCloud MCP Server. Nothing to install.
create_batch 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_batch 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_batch. 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_batch is provided by the ConsignCloud MCP Server MCP server (modellers/mcp-consigncloud). 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 →