Enhance a user prompt using prompt architect engine
AI agents use enhance_prompt to create or update resources in Prompt Architect — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Prompt Architect environment.
This tool writes modified data (an enhanced prompt) back to the user, making it a Write operation rather than Read-only. Severity is medium because misuse could generate misleading or manipulated prompts that guide downstream AI behavior in unintended directions, but the damage is reversible and depends on how the enhanced prompt is used.
From the tool's definition Tool performs 'enhance' action which creates or modifies a prompt artifact. The description states it uses a 'prompt architect engine' to transform user input, resulting in a new enriched prompt.
Attacks that exploit this kind of access
Enhance a user prompt using prompt architect engine. It is categorised as a Write tool in the Prompt Architect MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Prompt Architect MCP server in PolicyLayer and add a rule for enhance_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 Prompt Architect. Nothing to install.
enhance_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 enhance_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 enhance_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.
enhance_prompt is provided by the Prompt Architect MCP server (prompt-architect-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 →