Google releases Data Agent Kit to all users with 2 types of control
One control in the kit is advice that an agent can ignore, and one is an access rule that stops the tool.
Google released Data Agent Kit to all users after a test period that continued through the summer. The kit is free and open source. It connects coding agents to more than 15 Google data services and adds 37 skills, which are written guides for the agent. Google gives no test results.
How it works
The kit has 2 parts. Skills give best practice. MCP servers (tool links for agents) give live data on table data and tools. It operates in Claude Code, Codex, Cursor and other editors.
The two controls
One skill tells the agent to stop and get consent before a step that you cannot cancel, for example DROP TABLE. No rule makes the agent obey it. The other control is an IAM (access rule) deny policy that stops each MCP tool that changes data.
What is not known
A stopped tool continues to show in the tool list. The agent finds the stop only when it uses the tool. The rules apply to Google Cloud servers only. Ankit Dongre of viaSocket tells that tool results do not show if a slow write was complete.
Insight: Google and Microsoft put the control in different places
Microsoft keeps its agent rules in an admin surface and applies them at a gateway. Its access key goes to each model and tool, and a stop for each tool is in a preview tier. Google uses the IAM language that customers know. This seems a move to hold the layer of the agent rule, and the vendor that has it sets how customers work. Select the layer before you select the agent.
Sources
Posted
