create_task
AI agents use create_task to create or update resources in Tendem MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Tendem MCP environment.
Creating tasks is a reversible write operation that modifies system state by adding new records. It is not destructive (cannot be undone by deletion of the same record), does not execute arbitrary code, and does not involve financial transactions.
From the tool's definition Tool name 'create_task' indicates creation of new data/records within a task management system. No description provided, so classification relies on the semantic meaning of the verb 'create' and context from sibling tools (approve_task, cancel_task, get_task,…
Attacks that exploit this kind of access
create_task. It is categorised as a Write tool in the Tendem MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Tendem 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 Tendem 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 Tendem MCP server (toloka/tendem-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.