只导出增量内容的 Notion 元数据（需要提供已存在的论文列表）
AI agents use export_to_notion_update to create or update resources in Literature Review MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Literature Review MCP Server environment.
This tool writes/modifies data in an external service (Notion) by exporting incremental metadata updates. It is reversible (updates can be corrected or rolled back in Notion), so it is Write rather than Destructive.
From the tool's definition Tool name 'export_to_notion_update' and description indicating export of incremental content metadata to Notion.
Documented attack patterns abuse exactly the kind of access export_to_notion_update gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Literature Review MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for export_to_notion_update:
{
"version": "1",
"default": "deny",
"tools": {
"export_to_notion_update": {
"limits": [
{
"counter": "export_to_notion_update_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}export_to_notion_update 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.
只导出增量内容的 Notion 元数据（需要提供已存在的论文列表）. It is categorised as a Write tool in the Literature Review MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Literature Review MCP Server MCP server in PolicyLayer and add a rule for export_to_notion_update: 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 Literature Review MCP Server. Nothing to install.
export_to_notion_update 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 export_to_notion_update 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 export_to_notion_update. 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.
export_to_notion_update is provided by the Literature Review MCP Server MCP server (ydzat/literature-review-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Literature Review MCP Server, 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.
16 Literature Review MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.