AI agents use init_prompts 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.
init_prompts creates and modifies project metadata files (documentation and configuration) during project scanning. While it generates multiple files, it explicitly respects existing files and does not delete or irreversibly alter data. This is a Write operation because it creates new structured content (prompts system artifacts) that can be edited or removed.
From the tool's definition Tool description states it 'automatically generates prompts system' and creates files (context.md / todos.md / modules/). The phrase '已有文件不会覆盖' (existing files will not be overwritten) confirms it performs file creation/modification.
Attacks that exploit this kind of access
【初始化】扫描目标项目,自动生成 prompts 体系(context.md / todos.md / modules/)。已有文件不会覆盖。. 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 init_prompts: 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.
init_prompts 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 init_prompts 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 init_prompts. 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.
init_prompts 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 →