This record as markdown: /tools/com-files-python-mcp/list-bundle-registration.md
What List_Bundle_Registration does on Files Com
AI agents call List_Bundle_Registration 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 List_Bundle_Registration is rated Low
This tool retrieves a list of bundle registrations without creating, modifying, or deleting any data. It is a read-only operation that queries existing registrations, making it fall under the Read category with low severity since it has no side effects and minimal blast radius if misused by an AI agent.
From the tool's definition Tool name 'List_Bundle_Registration' and description 'List Share Link Registrations' indicate querying/retrieving registration data with no modification or deletion.
Attacks that exploit this kind of access
The rule that runs List_Bundle_Registration 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 List_Bundle_Registration, this is the rule to start with:
List_Bundle_Registration 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 List_Bundle_Registration call is checked against it from then on.
Questions about List_Bundle_Registration
List Share Link Registrations. 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 List_Bundle_Registration: 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.
List_Bundle_Registration 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 List_Bundle_Registration 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 List_Bundle_Registration. 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.
List_Bundle_Registration 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