AI agents use tasks_completeTask to create or update resources in Google MCP Remote — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Google MCP Remote environment.
This tool updates task metadata (completion status) but does not delete or destroy data—the task record remains and the action is reversible (task can be marked incomplete again). It is Write rather than Destructive. The medium severity reflects that misuse could clutter or falsify a user's task list, but the impact is limited to the tasks domain and the action is reversible.
From the tool's definition Tool name is 'tasks_completeTask' with description 'Mark a task as completed.' This modifies task state from incomplete to completed, changing persisted data.
Documented attack patterns abuse exactly the kind of access tasks_completeTask gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Google MCP Remote, and nothing reaches the server without passing your rules. This is the rule we recommend for tasks_completeTask:
{
"version": "1",
"default": "deny",
"tools": {
"tasks_completeTask": {
"limits": [
{
"counter": "tasks_completetask_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}tasks_completeTask 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.
Mark a task as completed. It is categorised as a Write tool in the Google MCP Remote MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Google MCP Remote MCP server in PolicyLayer and add a rule for tasks_completeTask: 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 MCP Remote. Nothing to install.
tasks_completeTask 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 tasks_completeTask 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 tasks_completeTask. 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.
tasks_completeTask is provided by the Google MCP Remote MCP server (vakharwalad23/google-mcp-remote). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Google MCP Remote, 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.
35 Google MCP Remote tools catalogued and risk-classified — across an index of 43,000+ MCP servers.