创建目录的文档(已实现功能的说明)
AI agents use create_doc to create or update resources in Code Analysis MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Code Analysis MCP Server environment.
The tool creates new documentation files/content, which is a reversible write operation. It does not execute arbitrary code, delete data, or move money. The medium severity reflects that creating documentation could potentially overwrite existing files or introduce misleading information, but the impact is limited to documentation artifacts rather than source code or critical data.
From the tool's definition Tool name 'create_doc' and description indicating it creates documentation for directories. The description translates to 'Create documentation for directories (explanation of implemented features)'. This is a write operation that creates new files/content.
Attacks that exploit this kind of access
创建目录的文档(已实现功能的说明). It is categorised as a Write tool in the Code Analysis MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Code Analysis MCP Server MCP server in PolicyLayer and add a rule for create_doc: 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 Code Analysis MCP Server. Nothing to install.
create_doc 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 create_doc 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 create_doc. 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.
create_doc is provided by the Code Analysis MCP Server MCP server (zeocax/code-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 →