Medium Risk

mega_export

Create a public link for a file/folder

Risk signalsAccepts file system path (path) · Handles credentials or secrets (password)

Part of the Mega server.

mega_export can modify Mega data, with no limits today. PolicyLayer puts allow, deny, and rate-limit rules on every call. Live in minutes.

SECURE MEGA →

Free to start. No card required.

AI agents use mega_export to create or modify resources in Mega. Write operations carry medium risk because an autonomous agent could trigger bulk unintended modifications. Rate limits prevent a single agent session from making hundreds of changes in rapid succession. Argument validation ensures the agent passes expected values.

Without a policy, an AI agent could call mega_export repeatedly, creating or modifying resources faster than any human could review. PolicyLayer's rate limiting ensures write operations happen at a controlled pace, and argument validation catches malformed or unexpected inputs before they reach Mega.

Write tools can modify data. A rate limit prevents runaway bulk operations from AI agents.

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "mega_export": {
      "limits": [
        {
          "counter": "mega_export_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

See the full Mega policy for all 20 tools.

Get this rule live on your own Mega server in minutes. PolicyLayer enforces it on every call, before it runs.

ENFORCE ON MY MEGA →

View all 20 tools →

These attack patterns abuse exactly the kind of access mega_export gives an agent. Each links to the full case and the policy that stops it:

Browse the full MCP Attack Database →

Every attack above starts with a tool call. PolicyLayer checks each one against your policy first, so mega_export only ever does what you allow.

SECURE MEGA →

Other write tools across the catalogue. The same approach applies to each: rate-limit and validate the arguments.

What does the mega_export tool do? +

Create a public link for a file/folder. 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.

How do I enforce a policy on mega_export? +

Register the Mega MCP server in PolicyLayer and add a rule for mega_export: 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.

What risk level is mega_export? +

mega_export is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit mega_export? +

Yes. Add a rate_limit block to the mega_export 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.

How do I block mega_export completely? +

Set action: deny in the PolicyLayer policy for mega_export. 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.

What MCP server provides mega_export? +

mega_export 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.

Enforce policy on every Mega tool call.

Deterministic rules across all 20 Mega tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

4,600+ MCP servers and 31,000+ tools scanned and risk-classified.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.