AI agents use batch_convert_pdfs to create or update resources in notebookLM2PPT — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your notebookLM2PPT environment.
Batch conversion of PDFs to PowerPoint creates new files or modifies existing ones, which is reversible (files can be deleted or regenerated). This is a Write operation rather than Read (it produces output artifacts), Execute (conversion is deterministic based on input), or Destructive (output is not irreversible).
From the tool's definition Tool name 'batch_convert_pdfs' indicates bulk conversion operations. Server description mentions 'convert PDF to PowerPoint presentations' and 'document processing.' The sibling tool 'convert_pdf_to_ppt' and server context indicate this creates or modifies…
Risk signalsBulk/mass operation — affects multiple targets
Documented attack patterns abuse exactly the kind of access batch_convert_pdfs gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and notebookLM2PPT, and nothing reaches the server without passing your rules. This is the rule we recommend for batch_convert_pdfs:
{
"version": "1",
"default": "deny",
"tools": {
"batch_convert_pdfs": {
"limits": [
{
"counter": "batch_convert_pdfs_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}batch_convert_pdfs 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.
batch_convert_pdfs. It is categorised as a Write tool in the notebookLM2PPT MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the notebookLM2PPT MCP server in PolicyLayer and add a rule for batch_convert_pdfs: 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 notebookLM2PPT. Nothing to install.
batch_convert_pdfs 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 batch_convert_pdfs 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 batch_convert_pdfs. 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.
batch_convert_pdfs is provided by the notebookLM2PPT MCP server (neosun100/notebooklm2ppt). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from notebookLM2PPT, 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.
3 notebookLM2PPT tools catalogued and risk-classified — across an index of 43,000+ MCP servers.