List all files contained in a project archive.
AI agents call td_list_project_files to retrieve information from Treasure Data MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and returns a list of files from a project archive without creating, modifying, deleting, or executing anything. It is a passive information retrieval operation consistent with other Read category tools on this server (td_list_databases, td_list_projects, td_list_tables, td_list_workflows).
From the tool's definition Tool name 'td_list_project_files' and description 'List all files contained in a project archive' indicate a retrieval operation with no side effects. The verb 'list' is explicitly read-only.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
List all files contained in a project archive. It is categorised as a Read tool in the Treasure Data MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Treasure Data MCP Server MCP server in PolicyLayer and add a rule for td_list_project_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 Treasure Data MCP Server. Nothing to install.
td_list_project_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 td_list_project_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 td_list_project_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.
td_list_project_files is provided by the Treasure Data MCP Server MCP server (knishioka/td-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 →