Unpublish a prompt, removing it from your public profile. The prompt is not deleted — it becomes private again.
AI agents use unpublish_prompt to create or update resources in PromptingBox MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your PromptingBox MCP Server environment.
This tool modifies the visibility state of a prompt from public to private. It is reversible (the prompt still exists and can be re-published), so it falls under Write rather than Destructive. Misuse could inadvertently hide publicly shared prompts, hence medium severity.
From the tool's definition Unpublish a prompt, removing it from your public profile. The prompt is not deleted — it becomes private again.
Attacks that exploit this kind of access
Unpublish a prompt, removing it from your public profile. The prompt is not deleted — it becomes private again. It is categorised as a Write tool in the PromptingBox MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the PromptingBox MCP Server MCP server in PolicyLayer and add a rule for unpublish_prompt: 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 PromptingBox MCP Server. Nothing to install.
unpublish_prompt 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_prompt 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_prompt. 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_prompt is provided by the PromptingBox MCP Server MCP server (promptingbox/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 →