Check studio content generation status and get URLs.
AI agents call studio_status to retrieve information from NotebookLM MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a read-only operation—querying the status of content generation and retrieving URLs. It has no side effects, does not create, modify, or delete data, and does not execute external operations or move resources. The blast radius of misuse is minimal; an attacker could only retrieve status information about existing generation tasks.
From the tool's definition Tool name 'studio_status' and description 'Check studio content generation status and get URLs' indicate a status query operation that retrieves information about existing content generation tasks without modifying data or triggering new operations.
Attacks that exploit this kind of access
Check studio content generation status and get URLs. It is categorised as a Read tool in the NotebookLM MCP Server MCP Server, which means it retrieves data without modifying state.
Register the NotebookLM MCP Server MCP server in PolicyLayer and add a rule for studio_status: 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.
studio_status 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 studio_status 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 studio_status. 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.
studio_status 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 →