agents_list_files
List files directly attached to this agent (agent-specific files, not shared collections). Returns file_id, title, status, and chunk_count for each file. chunk_count shows how many indexed chunks were created — 0 means the file is still processing. Use agents.add_file to attach a new file, or age...
This record as markdown: /tools/io-github-saloprj-dialogbrain/agents-list-files.md
What agents_list_files does on Dialogbrain
AI agents call agents_list_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 |
|---|---|---|---|
agent_id | integer | Yes | ID of the agent whose files to list |
Parameters from the server's own tool schema.
Why agents_list_files is rated Low
This is a straightforward read-only operation that retrieves and enumerates file metadata associated with an agent. It does not create, modify, delete, or execute anything. The mentions of agents.add_file and agents.remove_file are separate tools for those operations; this tool only queries state. Severity is low because unauthorized file listing poses minimal risk compared to file manipulation or message access.
From the tool's definition Tool performs a query/list operation ('List files'), returning metadata without modification. The description states it 'Returns file_id, title, status, and chunk_count' — pure retrieval of information about agent-specific files.
Attacks that exploit this kind of access
The rule that runs agents_list_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 agents_list_files, this is the rule to start with:
agents_list_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 agents_list_files call is checked against it from then on.
Questions about agents_list_files
List files directly attached to this agent (agent-specific files, not shared collections). Returns file_id, title, status, and chunk_count for each file. chunk_count shows how many indexed chunks were created — 0 means the file is still processing. Use agents.add_file to attach a new file, or agents.remove_file to detach one. It is categorised as a Read tool in the Dialogbrain MCP Server, which means it retrieves data without modifying state.
agents_list_files accepts 1 parameter: agent_id. Required: agent_id. 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 agents_list_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.
agents_list_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 agents_list_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 agents_list_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.
agents_list_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