prismic_update_custom_type · Prismic Content MCP

WHAT IT DOES

What prismic_update_custom_type does on Prismic Content MCP

AI agents use prismic_update_custom_type to create or update resources in Prismic Content MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Prismic Content MCP environment.

WHY IT NEEDS A POLICY

Why prismic_update_custom_type needs a policy

The tool updates custom types, which are content schema definitions in Prismic. This is a Write operation because it modifies data reversibly (updates can be undone or reverted). Severity is high because custom type changes can affect the structure and behavior of all documents using those types, potentially breaking content dependencies across the repository.

From the tool's definition Tool name contains 'update' which modifies data reversibly; server description explicitly mentions 'managing' content and 'secure write operations'; the tool operates on Custom Types API which controls content schema definitions.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

prismic_update_custom_type Rate-limited

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

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "prismic_update_custom_type": {
      "limits": [
        {
          "counter": "prismic_update_custom_type_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Prismic Content MCP, so you can run agents against it safely.

FAQ

Questions about prismic_update_custom_type

What does the prismic_update_custom_type tool do? +

prismic_update_custom_type. It is categorised as a Write tool in the Prismic Content MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on prismic_update_custom_type? +

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

What risk level is prismic_update_custom_type? +

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

Can I rate-limit prismic_update_custom_type? +

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

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

prismic_update_custom_type is provided by the Prismic Content MCP server (rahulpowar/prismic-content-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.