Update an existing prompt
AI agents use update_prompt to create or update resources in Prompteka MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Prompteka MCP Server environment.
Updating a prompt modifies data but is reversible—the original can be restored by editing again or reverting. This is a Write operation. Severity is low because the blast radius of misuse is limited to local prompt library modifications on a single macOS system with no external financial or system-level impact.
From the tool's definition Tool name is 'update_prompt' and description states 'Update an existing prompt', which modifies existing data reversibly. The sibling tools include destructive operations (delete_prompt, delete_folder) which are separate, indicating update is non-destructive.
Attacks that exploit this kind of access
Update an existing prompt. It is categorised as a Write tool in the Prompteka MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Prompteka MCP Server 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 Prompteka MCP Server. 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 Prompteka MCP Server MCP server (webdevguyrg/prompteka-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 →