search
AI agents call search to retrieve information from LibreOffice MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool is named 'search', which in the context of a LibreOffice document server indicates retrieving or querying document content. Without a description, confidence is moderately reduced, but search functionality characteristically performs read-only operations matching the 'Read' category. No evidence suggests it modifies, deletes, executes code, or involves financial operations.
From the tool's definition Tool name 'search' on a document manipulation server with no description provided, but search operations are typically read-only queries of document content without side effects.
Attacks that exploit this kind of access
search. It is categorised as a Read tool in the LibreOffice MCP Server MCP Server, which means it retrieves data without modifying state.
Register the LibreOffice MCP Server MCP server in PolicyLayer and add a rule for search: 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 LibreOffice MCP Server. Nothing to install.
search 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 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. 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 is provided by the LibreOffice MCP Server MCP server (jwingnut/mcp-libre). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
search is one line of LibreOffice MCP Server's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →