project_doc_update · ProjectDoc MCP: Risk & Policy

WHAT IT DOES

What project_doc_update does on ProjectDoc

AI agents use project_doc_update to create or update resources in ProjectDoc — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your ProjectDoc environment.

WHY IT NEEDS A POLICY

Why project_doc_update needs a policy

This tool modifies existing data (project documentation entries) in a reversible manner. It is not a read operation (it changes state), not destructive (updates are reversible and do not delete), not an execute operation (no code/command execution), and not financial. Write is the appropriate category.

From the tool's definition Tool name 'project_doc_update' and description '更新条目字段。只更新提供的非空字段。' (Update entry fields. Only update provided non-empty fields.) indicate modification of existing documentation entries.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

project_doc_update Rate-limited

project_doc_update stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "project_doc_update": {
      "limits": [
        {
          "counter": "project_doc_update_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches ProjectDoc, so you can run agents against it safely.

FAQ

Questions about project_doc_update

What does the project_doc_update tool do? +

更新条目字段。只更新提供的非空字段。. It is categorised as a Write tool in the ProjectDoc MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on project_doc_update? +

Register the ProjectDoc MCP server in PolicyLayer and add a rule for project_doc_update: 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 ProjectDoc. Nothing to install.

What risk level is project_doc_update? +

project_doc_update is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit project_doc_update? +

Yes. Add a rate_limit block to the project_doc_update 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.

How do I block project_doc_update completely? +

Set action: deny in the PolicyLayer policy for project_doc_update. 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.

What MCP server provides project_doc_update? +

project_doc_update is provided by the ProjectDoc MCP server (yarrow-cai/project-doc). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.