data_table_create
AI agents use data_table_create to create or update resources in NotebookLM MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your NotebookLM MCP Server environment.
The tool name ends in '_create', suggesting it generates/writes a new data table. The server context shows a pattern of content creation tools (flashcards_create, infographic_create, mind_map_create), so this fits the Write category as a reversible content creation action. Confidence is lowered due to the empty description.
From the tool's definition Tool name 'data_table_create' and empty description. Based on the 'create' suffix and server context of generating content artifacts (audio, infographics, slide decks, etc.), this likely creates a data table artifact within a notebook.
Attacks that exploit this kind of access
data_table_create. It is categorised as a Write tool in the NotebookLM MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the NotebookLM MCP Server MCP server in PolicyLayer and add a rule for data_table_create: 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 NotebookLM MCP Server. Nothing to install.
data_table_create 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 data_table_create 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 data_table_create. 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.
data_table_create is provided by the NotebookLM MCP Server MCP server (ran-ai-agency/notebooklm-mcp). 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 →