This record as markdown: /tools/com-files-python-mcp/create-bundle-recipient.md
What Create_Bundle_Recipient does on Files Com
AI agents use Create_Bundle_Recipient to create or update resources in Files Com, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Files Com environment.
Why Create_Bundle_Recipient is rated Medium
This tool creates a new recipient entry for a share link, which modifies data in the Files.com environment by adding access grants. It is reversible (recipients can be removed), making it Write rather than Destructive. The severity is high because improper use could grant unintended file access to unauthorized parties, potentially exposing sensitive data depending on what bundle is being shared.
From the tool's definition Tool name is 'Create_Bundle_Recipient' and description states 'Create Share Link Recipient'. The verb 'Create' indicates this tool adds a new recipient to a share link bundle, which is a reversible data modification.
Attacks that exploit this kind of access
The rule that runs Create_Bundle_Recipient 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 Create_Bundle_Recipient, this is the rule to start with:
Create_Bundle_Recipient stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. 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 Create_Bundle_Recipient call is checked against it from then on.
Questions about Create_Bundle_Recipient
Create Share Link Recipient. It is categorised as a Write tool in the Files Com MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Files Com MCP server in PolicyLayer and add a rule for Create_Bundle_Recipient: 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.
Create_Bundle_Recipient is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the Create_Bundle_Recipient 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 Create_Bundle_Recipient. 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.
Create_Bundle_Recipient 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