Get the current status of full-text indexing background processing.
AI agents call zotero_get_fulltext_indexing_status to retrieve information from Zotero MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries the state of an indexing process. It is purely informational and does not create, modify, delete, or execute operations. The absence of action verbs like 'start', 'stop', 'trigger', or 'clear' confirms it is a retrieval/read-only operation.
From the tool's definition Tool name contains 'get' and description states it retrieves 'current status of full-text indexing background processing' — a query operation with no data modification or side effects.
Attacks that exploit this kind of access
Get the current status of full-text indexing background processing. It is categorised as a Read tool in the Zotero MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Zotero MCP Server MCP server in PolicyLayer and add a rule for zotero_get_fulltext_indexing_status: 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 MCP Server. Nothing to install.
zotero_get_fulltext_indexing_status 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 zotero_get_fulltext_indexing_status 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 zotero_get_fulltext_indexing_status. 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.
zotero_get_fulltext_indexing_status is provided by the Zotero MCP Server MCP server (tspspi/zotero-mcp-postgres-ollama-fulltext). 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 →