prismic_add_media
AI agents use prismic_add_media 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.
The tool adds (creates/uploads) media to Prismic's Asset API. This is a reversible write operation—media can be deleted or replaced—not a read-only query or irreversible destruction. The 'add' verb and media management context confirm it creates new asset entries. Confidence is moderate-high because the description is empty, but the name and server context provide clear semantic intent.
From the tool's definition Tool name 'prismic_add_media' indicates creating or uploading media assets. The server description mentions 'managing media assets' and 'secure write operations', confirming this is a write action.
Attacks that exploit this kind of access
prismic_add_media. 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_add_media: 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_add_media 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_add_media 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_add_media. 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_add_media 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 →