验证 Zotero 原生字段数量、占位符状态和 bibliography 是否位于参考文献标题后。
AI agents call validate_zotero_document to retrieve information from Zotero Word without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool performs validation checks (验证 = verify/validate) on Zotero native fields, placeholders, and bibliography location. These are inspection and analysis operations that read document properties to confirm compliance with expected structure. No modifications, deletions, executions, or financial transactions occur.
From the tool's definition Tool name 'validate_zotero_document' and description indicating verification of field counts, placeholder status, and bibliography position—actions that inspect and validate document state without modifying content.
Attacks that exploit this kind of access
验证 Zotero 原生字段数量、占位符状态和 bibliography 是否位于参考文献标题后。. It is categorised as a Read tool in the Zotero Word MCP Server, which means it retrieves data without modifying state.
Register the Zotero Word MCP server in PolicyLayer and add a rule for validate_zotero_document: 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 Zotero Word. Nothing to install.
validate_zotero_document 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 validate_zotero_document 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 validate_zotero_document. 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.
validate_zotero_document is provided by the Zotero Word MCP server (zhangchaokai1/zotero-word-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 →