search_files
Search files and attachments across the workspace — by content, filename, document type, or origin. For message content use search.messages; for links use search.links.
This record as markdown: /tools/io-github-saloprj-dialogbrain/search-files.md
What search_files does on Dialogbrain
AI agents call search_files to retrieve information from Dialogbrain without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
limit | integer | — | Maximum files to return. |
query | string | — | What to search for (content or filename). |
file_origin | string | — | File origin: 'generated' (created by tools), 'received' (from messages), 'uploaded' (manual). Use 'generated' for files the user created/sent. OMIT to include a |
document_type | string | — | Filter by document category. OMIT unless the user explicitly mentions one — picking a value narrows the search and is a common cause of zero-result mistakes. |
attachment_name | string | — | Exact filename filter. OMIT to skip (do NOT pass an empty string). |
Parameters from the server's own tool schema.
Why search_files is rated Low
This tool retrieves and queries file data without creating, modifying, deleting, or executing operations. It is a pure read operation for discovering files within the workspace. Low severity because search operations have minimal blast radius — they only expose data that already exists and cannot cause harm through misuse beyond information disclosure.
From the tool's definition Tool name is 'search_files' and description states it 'Search files and attachments across the workspace' with filtering options.
Attacks that exploit this kind of access
The rule that runs search_files safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Dialogbrain, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For search_files, this is the rule to start with:
search_files is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Dialogbrain, apply this rule, and every search_files call is checked against it from then on.
Questions about search_files
Search files and attachments across the workspace — by content, filename, document type, or origin. For message content use search.messages; for links use search.links. It is categorised as a Read tool in the Dialogbrain MCP Server, which means it retrieves data without modifying state.
search_files accepts 5 parameters: limit, query, file_origin, document_type, attachment_name. The full parameter table on this page comes from the server's own tool schema.
Register the Dialogbrain MCP server in PolicyLayer and add a rule for search_files: 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 Dialogbrain. Nothing to install.
search_files 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_files 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_files. 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_files is provided by the Dialogbrain MCP server (https://api.dialogbrain.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Dialogbrain, and thousands of servers like it.
This server
Across the catalogue