AI agents use create_task to create or update resources in Vaiz MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Vaiz MCP environment.
This tool creates new data in the Vaiz workspace, making it a Write operation. The severity is medium because creating tasks could be abused to clutter the workspace or inject misleading work items that might influence team decisions or workflows, but the operation is reversible through deletion or editing. The high confidence reflects the clear intent from both the name and description.
From the tool's definition Tool name 'create_task' and description 'Create a new task in the Vaiz workspace' indicate the tool creates new data structures (tasks) in a reversible manner. The action modifies workspace state but is not destructive or financial.
Attacks that exploit this kind of access
Create a new task in the Vaiz workspace. It is categorised as a Write tool in the Vaiz MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Vaiz MCP server in PolicyLayer and add a rule for create_task: 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 Vaiz MCP. Nothing to install.
create_task 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_task 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_task. 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_task is provided by the Vaiz MCP server (vaizcom/vaiz-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 →