prismic_upsert_documents
AI agents use prismic_upsert_documents 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.
Upsert operations create or modify data reversibly without permanent deletion, fitting the Write category. Severity is high because bulk document updates in a content management system could affect published content, user-facing data, or business-critical information across multiple records. While the tool description is empty, the name and server context provide strong evidence.
From the tool's definition Tool name 'prismic_upsert_documents' indicates creation or modification of documents. 'Upsert' is a standard database operation meaning 'update if exists, insert if not', which is reversible modification.
Attacks that exploit this kind of access
prismic_upsert_documents. 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.
Register the Prismic Content MCP server in PolicyLayer and add a rule for prismic_upsert_documents: 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.
prismic_upsert_documents 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 prismic_upsert_documents 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 prismic_upsert_documents. 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.
prismic_upsert_documents 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.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →