Get status of the Lucene MCP server (index path, doc count).
AI agents call lucene_status to retrieve information from Mcp Lucene without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool only retrieves and queries status information about the Lucene server—specifically the index path and document count. It has no side effects, does not modify data, execute code, or delete anything. It is a pure read operation returning server metadata.
From the tool's definition Tool name 'lucene_status' and description 'Get status of the Lucene MCP server (index path, doc count)' indicate retrieval of server metadata and statistics without modification.
Attacks that exploit this kind of access
Get status of the Lucene MCP server (index path, doc count). It is categorised as a Read tool in the Mcp Lucene MCP Server, which means it retrieves data without modifying state.
Register the Mcp Lucene MCP server in PolicyLayer and add a rule for lucene_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 Mcp Lucene. Nothing to install.
lucene_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 lucene_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 lucene_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.
lucene_status is provided by the Mcp Lucene MCP server (vivekkumarneu/mcp-lucene-server). 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 →