Share a folder with another MEGA user
AI agents use mega_share to create or update resources in Mega — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Mega environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
path | string | Yes | Remote folder path to share |
email | string | Yes | Email of user to share with |
access_level | string | — | Access level: 'r' (read), 'rw' (read-write), 'full' (full access) |
Parameters from the server's own tool schema.
Sharing a folder grants access to another user, which is a reversible modification of access permissions. It does not delete data, execute code, or involve financial transactions. Misuse could expose sensitive data to unintended parties, hence medium severity.
From the tool's definition Share a folder with another MEGA user
Risk signalsAccepts file system path (path)
Documented attack patterns abuse exactly the kind of access mega_share gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Mega, and nothing reaches the server without passing your rules. This is the rule we recommend for mega_share:
{
"version": "1",
"default": "deny",
"tools": {
"mega_share": {
"limits": [
{
"counter": "mega_share_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}mega_share 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.
Free to start. No card required.
Share a folder with another MEGA user. It is categorised as a Write tool in the Mega MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
mega_share accepts 3 parameters: path, email, access_level. Required: path, email. The full parameter table on this page comes from the server's own tool schema.
Register the Mega MCP server in PolicyLayer and add a rule for mega_share: 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 Mega. Nothing to install.
mega_share 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 mega_share 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 mega_share. 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.
mega_share is provided by the Mega MCP server (mega-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Mega, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
20 Mega tools catalogued and risk-classified — across an index of 43,000+ MCP servers.