Create a new task. Note: the Google Tasks API only supports due dates, not times.
AI agents use create-task to create or update resources in Google Tasks — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Google Tasks environment.
The tool creates a new task, which is reversible (tasks can be deleted via the sibling delete-task tool). This is a standard write operation with minimal blast radius—creating a task does not modify existing data, execute code, delete anything, or move money. Severity is low because the impact is limited to task management data, and any unintended tasks created can be easily removed.
From the tool's definition Tool name is 'create-task' and description states 'Create a new task.' This is a write operation that creates new data in Google Tasks.
Attacks that exploit this kind of access
Create a new task. Note: the Google Tasks API only supports due dates, not times. It is categorised as a Write tool in the Google Tasks MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Google Tasks 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 Google Tasks. 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 Google Tasks MCP server (scottie-will/google-tasks-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 →