AI agents use convert_pdf_to_ppt 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.
The tool creates or modifies presentation documents by converting PDF input into PowerPoint format. This is a reversible write operation—the output can be edited, deleted, or regenerated. It does not execute arbitrary code, delete data irreversibly, or move money.
From the tool's definition Tool name 'convert_pdf_to_ppt' and server description states it 'convert[s] NotebookLM PDF exports into high-quality PowerPoint presentations' with 'automatic watermark removal and vector graphics preservation'.
Documented attack patterns abuse exactly the kind of access convert_pdf_to_ppt 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 convert_pdf_to_ppt:
{
"version": "1",
"default": "deny",
"tools": {
"convert_pdf_to_ppt": {
"limits": [
{
"counter": "convert_pdf_to_ppt_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}convert_pdf_to_ppt 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.
convert_pdf_to_ppt. 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 convert_pdf_to_ppt: 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.
convert_pdf_to_ppt 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 convert_pdf_to_ppt 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 convert_pdf_to_ppt. 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.
convert_pdf_to_ppt 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.