Add a task or reminder
AI agents use add_task to create or update resources in Google Workspace MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Google Workspace MCP Server environment.
This tool creates new task/reminder records without permanently deleting data or executing arbitrary code. It modifies the user's task list state but the operation is reversible (tasks can be edited or deleted later). Severity is medium because misconfigured task creation could spam the user's task list or create misleading reminders, but lacks the irreversibility of destructive operations or financial impact.
From the tool's definition Tool name 'add_task' and description 'Add a task or reminder' indicate creation of new data in Google Workspace services (likely Google Tasks, Calendar, or local storage). The verb 'add' is characteristic of reversible write operations.
Attacks that exploit this kind of access
Add a task or reminder. It is categorised as a Write tool in the Google Workspace MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Google Workspace MCP Server MCP server in PolicyLayer and add a rule for add_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 Workspace MCP Server. Nothing to install.
add_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 add_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 add_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.
add_task is provided by the Google Workspace MCP Server MCP server (pbulbule13/google-mcp-server). 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 →