AI agents use create_task 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.
Creating a task is a reversible modification operation (tasks can be deleted later via the delete_task sibling tool), so it falls under Write rather than Execute or Destructive. Severity is medium because creating tasks is relatively low-impact compared to deletion or financial operations, but misuse could spam or pollute a user's task list. The high confidence reflects the clear semantics of the 'create' operation.
From the tool's definition Tool description states 'Create a new task in Google Tasks' - a create operation that adds new data to the system.
Documented attack patterns abuse exactly the kind of access create_task gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Google Tasks MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for create_task:
{
"version": "1",
"default": "deny",
"tools": {
"create_task": {
"limits": [
{
"counter": "create_task_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}create_task stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
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_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 MCP Server. 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 MCP server (mstfe/mcp-google-tasks). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Google Tasks MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
4 Google Tasks MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.