prismic_update_shared_slice · Prismic Content MCP

WHAT IT DOES

What prismic_update_shared_slice does on Prismic Content MCP

AI agents use prismic_update_shared_slice 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_shared_slice needs a policy

This tool modifies existing shared slice definitions, which are reusable content components. Updates are reversible (can be updated again or reverted), placing it in the Write category rather than Destructive.

From the tool's definition Tool name 'prismic_update_shared_slice' and description 'Update an existing Shared Slice model' indicate modification of existing data. The server description notes 'secure write operations' confirming this is a write-capable tool.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

prismic_update_shared_slice Rate-limited

prismic_update_shared_slice 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_shared_slice": {
      "limits": [
        {
          "counter": "prismic_update_shared_slice_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_shared_slice

What does the prismic_update_shared_slice tool do? +

Update an existing Shared Slice model. 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_shared_slice? +

Register the Prismic Content MCP server in PolicyLayer and add a rule for prismic_update_shared_slice: 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_shared_slice? +

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

Can I rate-limit prismic_update_shared_slice? +

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

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

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