AI agents call company_search to retrieve information from Local without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
query | string | Yes | The search query. This is what you want to search for. |
datasources | array | — | Optional list of data sources to search in. Examples: "github", "gdrive", "confluence", "jira". |
Parameters from the server's own tool schema.
This tool performs a search operation to locate and retrieve company documents and data from specified datasources (drive, confluence). It has no side effects, does not modify data, execute code, delete anything, or move money. It is a straightforward information retrieval tool, making it a Read category with low severity.
From the tool's definition Tool description states 'Find relevant company documents and data' and example shows a search query. The tool retrieves information without modifying or executing operations.
Risk signalsAccepts freeform code/query input (query)
Attacks that exploit this kind of access
Find relevant company documents and data Example request: { "query": "What are the company holidays this year?", "datasources": ["drive", "confluence"] }. It is categorised as a Read tool in the Local MCP Server, which means it retrieves data without modifying state.
company_search accepts 2 parameters: query, datasources. Required: query. The full parameter table on this page comes from the server's own tool schema.
Register the Local MCP server in PolicyLayer and add a rule for company_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 Local. Nothing to install.
company_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 company_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 company_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.
company_search is provided by the Local MCP server (@gleanwork/local-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 →