write_and_log · Project Context Map MCP: Risk & Policy

WHAT IT DOES

What write_and_log does on Project Context Map

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

WHY IT NEEDS A POLICY

Why write_and_log needs a policy

This tool creates or modifies file content and log entries, which are reversible operations. It does not delete data (would be Destructive), execute arbitrary code (would be Execute), or move money (would be Financial). While it can modify project files, the changes are logged and can be undone through version control.

From the tool's definition Tool description states 'Writes file content and appends an entry to the .project.md Change Log.' The verbs 'writes' and 'appends' indicate reversible data modifications.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

write_and_log Rate-limited

write_and_log 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": {
    "write_and_log": {
      "limits": [
        {
          "counter": "write_and_log_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 Project Context Map, so you can run agents against it safely.

FAQ

Questions about write_and_log

What does the write_and_log tool do? +

Writes file content and appends an entry to the .project.md Change Log. It is categorised as a Write tool in the Project Context Map MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on write_and_log? +

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

What risk level is write_and_log? +

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

Can I rate-limit write_and_log? +

Yes. Add a rate_limit block to the write_and_log 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 write_and_log completely? +

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

write_and_log is provided by the Project Context Map MCP server (tamojit-123/project-context-map-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.