Unpublish an AI action to remove it from use in the Contentful web app
AI agents use unpublish_ai_action to create or update resources in Contentful MCP Remote Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Contentful MCP Remote Server environment.
Unpublishing changes the state of an AI action (making it inactive/unavailable) but is generally reversible — the action can be republished. This is a state modification (Write) rather than a deletion (Destructive). The blast radius is medium as it affects availability of the AI action in production but can be undone.
From the tool's definition Unpublish an AI action to remove it from use in the Contentful web app
Attacks that exploit this kind of access
Unpublish an AI action to remove it from use in the Contentful web app. It is categorised as a Write tool in the Contentful MCP Remote Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Contentful MCP Remote Server MCP server in PolicyLayer and add a rule for unpublish_ai_action: 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 MCP Remote Server. Nothing to install.
unpublish_ai_action 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 unpublish_ai_action 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 unpublish_ai_action. 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.
unpublish_ai_action is provided by the Contentful MCP Remote Server MCP server (renzoqcad/contentful-express-mcp-server). 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 →