Medium Risk

export_space

Export entire space to file

Risk signalsExports all content data

Part of the Contentful server.

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

SECURE CONTENTFUL →

Free to start. No card required.

AI agents use export_space to create or modify resources in Contentful. 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 export_space 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 Contentful.

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

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

See the full Contentful policy for all 61 tools.

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

ENFORCE ON MY CONTENTFUL →

View all 61 tools →

These attack patterns abuse exactly the kind of access export_space 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 export_space only ever does what you allow.

SECURE CONTENTFUL →

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

What does the export_space tool do? +

Export entire space to file. It is categorised as a Write tool in the Contentful MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on export_space? +

Register the Contentful MCP server in PolicyLayer and add a rule for export_space: 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 Contentful. Nothing to install.

What risk level is export_space? +

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

Can I rate-limit export_space? +

Yes. Add a rate_limit block to the export_space 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 export_space completely? +

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

export_space is provided by the Contentful MCP server (@@contentful/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 Contentful tool call.

Deterministic rules across all 61 Contentful 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.