AI agents call search-documents to retrieve information from Lucid without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and retrieves document metadata (names and IDs) based on search criteria. It has no side effects, does not create, modify, delete, or execute anything. It is a straightforward read operation consistent with search and list functionality.
From the tool's definition Tool description states 'Search Lucid documents in your account returns document list with namesname and their IDs. Supports filtering by keywords' — this is a search/retrieval operation with no modification capability.
Attacks that exploit this kind of access
Search Lucid documents in your account returns document list with namesname and their IDs. Supports filtering by keywords. It is categorised as a Read tool in the Lucid MCP Server, which means it retrieves data without modifying state.
Register the Lucid MCP server in PolicyLayer and add a rule for search-documents: 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 Lucid. Nothing to install.
search-documents 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 search-documents 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 search-documents. 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.
search-documents is provided by the Lucid MCP server (lucid-mcp-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 →