AI agents invoke safe_publish to trigger actions in Prompts. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
This tool executes a multi-step pipeline: it publishes to npm (external package registry), pushes to git (modifies remote repository), bumps version numbers, updates README, and runs npm link. These are chained external operations with broad blast radius — publishing to npm is irreversible in practical terms and affects all downstream consumers.
From the tool's definition 一键完成隐私审计 + 版本 bump + npm publish + git push + npm link + README 更新 (one-click: privacy audit + version bump + npm publish + git push + npm link + README update)
Attacks that exploit this kind of access
【安全发布】一键完成隐私审计 + 版本 bump + npm publish + git push + npm link + README 更新。. It is categorised as a Execute tool in the Prompts MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Prompts MCP server in PolicyLayer and add a rule for safe_publish: 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 Prompts. Nothing to install.
safe_publish is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the safe_publish 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 safe_publish. 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.
safe_publish is provided by the Prompts MCP server (thana0623/pmcp-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 →