保存切分后的章节内容到本地文件,并记录章节元信息。
AI agents use save_chapter to create or update resources in Bun Novel Processor MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Bun Novel Processor MCP environment.
This tool creates and writes chapter files and their associated metadata to persistent storage. It modifies the local filesystem reversibly (files can be edited or deleted later), making it a Write operation.
From the tool's definition Tool name 'save_chapter' and description '保存切分后的章节内容到本地文件,并记录章节元信息' (Save segmented chapter content to local file and record chapter metadata) indicate creation/modification of files and metadata records.
Attacks that exploit this kind of access
保存切分后的章节内容到本地文件,并记录章节元信息。. It is categorised as a Write tool in the Bun Novel Processor MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Bun Novel Processor MCP server in PolicyLayer and add a rule for save_chapter: 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 Bun Novel Processor MCP. Nothing to install.
save_chapter 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 save_chapter 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 save_chapter. 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.
save_chapter is provided by the Bun Novel Processor MCP server (tietiezhi-1216/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 →