Get expanded context around a search result chunk.
AI agents call get_chunk_context to retrieve information from Mcp Zotero without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and queries data from Zotero search results without side effects. It expands context around chunks, which is a read-only operation. The blast radius of misuse is minimal—an agent could only access more context from existing search results, not modify or delete library data, execute code, or commit financial actions.
From the tool's definition Tool name 'get_chunk_context' and description 'Get expanded context around a search result chunk' indicate retrieval of contextual data around existing search results. No modification, deletion, or execution of external operations.
Attacks that exploit this kind of access
Get expanded context around a search result chunk. It is categorised as a Read tool in the Mcp Zotero MCP Server, which means it retrieves data without modifying state.
Register the Mcp Zotero MCP server in PolicyLayer and add a rule for get_chunk_context: 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 Mcp Zotero. Nothing to install.
get_chunk_context 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 get_chunk_context 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 get_chunk_context. 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.
get_chunk_context is provided by the Mcp Zotero MCP server (nealcaren/mcp-zotero). 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 →