AI agents use confirm_direction to create or update resources in Prompts — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Prompts environment.
This tool creates or modifies project direction documentation (direction.md) based on user confirmation during an AI dialogue. While the write is reversible (the file can be edited or deleted later), it does modify persistent project state. It does not execute arbitrary code, delete data irreversibly, or move money, so Write is the appropriate category.
From the tool's definition Tool description states it 'saves target, constraints, and acceptance criteria to direction.md' — this is a create/modify operation that writes data to a persistent file. The tool performs a reversible write action ('保存' = save/persist).
Attacks that exploit this kind of access
【方向确认】AI 追问澄清后,用户确认方向时调用。保存目标、约束、验收标准到 direction.md。对话式追问由 AI 自然完成,此工具只负责持久化确认结果。. It is categorised as a Write tool in the Prompts MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Prompts MCP server in PolicyLayer and add a rule for confirm_direction: 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.
confirm_direction 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 confirm_direction 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 confirm_direction. 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.
confirm_direction 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 →