AI agents call search to retrieve information from Google Tasks MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The search function queries existing tasks without modifying, deleting, or executing external operations. It returns data only and has no destructive or state-changing effects. Although the server as a whole includes destructive tools (delete, clear), this specific tool is purely informational.
From the tool's definition Tool name is 'search' and description states 'Search for a task in Google Tasks' — a retrietary operation with no side effects.
Documented attack patterns abuse exactly the kind of access search 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 search:
{
"version": "1",
"default": "deny",
"tools": {
"search": {}
}
}search is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Search for a task in Google Tasks. It is categorised as a Read tool in the Google Tasks MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Google Tasks MCP Server MCP server in PolicyLayer and add a rule for search: 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.
search is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the search 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 search. 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.
search is provided by the Google Tasks MCP Server MCP server (zcaceres/gtasks-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 7 Google Tasks MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
7 Google Tasks MCP Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.