将数据库中的单篇文献综述导出为 Markdown 文件
AI agents use export_individual_review_to_md 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 creates or generates new Markdown files from existing database data. This is a Write operation (creates/modifies data reversibly) rather than Read (it actively transforms and exports data to a new format/location) or Destructive (the export itself does not delete source data).
From the tool's definition Tool name 'export_individual_review_to_md' and description indicate it exports a single literature review from a database to a Markdown file. The action is writing/creating output files, which is reversible.
Documented attack patterns abuse exactly the kind of access export_individual_review_to_md 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_individual_review_to_md:
{
"version": "1",
"default": "deny",
"tools": {
"export_individual_review_to_md": {
"limits": [
{
"counter": "export_individual_review_to_md_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}export_individual_review_to_md 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.
将数据库中的单篇文献综述导出为 Markdown 文件. 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_individual_review_to_md: 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_individual_review_to_md 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_individual_review_to_md 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_individual_review_to_md. 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_individual_review_to_md 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.