This record as markdown: /tools/com-files-python-mcp/find-bundle.md
What Find_Bundle does on Files Com
AI agents call Find_Bundle to retrieve information from Files Com without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why Find_Bundle is rated Low
This tool retrieves or queries data about an existing bundle share link without creating, modifying, or deleting any data. It has no side effects beyond returning information. This is clearly a Read category tool with low severity since it only exposes existing share link information.
From the tool's definition Tool is described as 'Show Share Link' which retrieves and displays information about a bundle/share link. The verb 'Show' and the action of displaying an existing share link indicates a read-only operation with no data modification or deletion.
Attacks that exploit this kind of access
The rule that runs Find_Bundle safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Files Com, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For Find_Bundle, this is the rule to start with:
Find_Bundle 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 Files Com, apply this rule, and every Find_Bundle call is checked against it from then on.
Questions about Find_Bundle
Show Share Link. It is categorised as a Read tool in the Files Com MCP Server, which means it retrieves data without modifying state.
Register the Files Com MCP server in PolicyLayer and add a rule for Find_Bundle: 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 Files Com. Nothing to install.
Find_Bundle 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 Find_Bundle 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 Find_Bundle. 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.
Find_Bundle is provided by the Files Com MCP server (files-com-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Files Com, and thousands of servers like it.
This server
Across the catalogue