Create a new task in Google Tasks
AI agents use create to create or update resources in Google Tasks MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Google Tasks MCP Server environment.
The tool performs a reversible data modification (task creation) without destructive intent. While it modifies state, tasks can be deleted or updated, making it Write rather than Destructive. Severity is medium because misuse could clutter task lists or create misleading tasks, but the impact is limited to task data with no financial or system-level consequences.
From the tool's definition Tool creates a new task in Google Tasks; the description explicitly states 'Create a new task'. This is a write operation that adds data to the user's task management system.
Attacks that exploit this kind of access
Create a new task in Google Tasks. It is categorised as a Write tool in the Google Tasks MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Google Tasks MCP Server MCP server in PolicyLayer and add a rule for create: 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 MCP Server. Nothing to install.
create 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 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. 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 is provided by the Google Tasks MCP Server MCP server (tonywmnix/gtasks-mcp-cf). 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 →