AI agents use update-prompt to create or update resources in MCP Prompt Manager — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your MCP Prompt Manager environment.
This tool creates or modifies data in a reversible manner—a hallmark of the Write category. An AI agent misusing it could overwrite important prompts, but the changes are not irreversible (backups/version control exist on this server, as indicated by 'compare-prompt-versions').
From the tool's definition Tool name 'update-prompt' and description 'Update an existing prompt file' indicate the tool modifies existing data reversibly. The action is Create/Update (Write category), not deletion or destruction.
Documented attack patterns abuse exactly the kind of access update-prompt gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and MCP Prompt Manager, and nothing reaches the server without passing your rules. This is the rule we recommend for update-prompt:
{
"version": "1",
"default": "deny",
"tools": {
"update-prompt": {
"limits": [
{
"counter": "update-prompt_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}update-prompt stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Update an existing prompt file. It is categorised as a Write tool in the MCP Prompt Manager MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the MCP Prompt Manager MCP server in PolicyLayer and add a rule for update-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 MCP Prompt Manager. Nothing to install.
update-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 update-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 update-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.
update-prompt is provided by the MCP Prompt Manager MCP server (tae4an/mcp-prompt-manager). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from MCP Prompt Manager, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
33 MCP Prompt Manager tools catalogued and risk-classified — across an index of 43,000+ MCP servers.