mission_log_decision · Notion MCP: Risk & Policy

WHAT IT DOES

What mission_log_decision does on Notion MCP

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

WHY IT NEEDS A POLICY

Why mission_log_decision needs a policy

This tool writes a new decision log entry to Notion, which is a reversible write operation. The server description confirms it supports 'create and append operations' and the tool itself is tagged 'safe_write'. No deletion, execution, or financial action is involved. Severity is low because logging decisions has minimal blast radius even if misused.

From the tool's definition 'Log an architecture, product, business, security, or implementation decision to Notion. Risk: safe_write.'

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

mission_log_decision Rate-limited

mission_log_decision 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": {
    "mission_log_decision": {
      "limits": [
        {
          "counter": "mission_log_decision_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 Notion MCP, so you can run agents against it safely.

FAQ

Questions about mission_log_decision

What does the mission_log_decision tool do? +

Log an architecture, product, business, security, or implementation decision to Notion. Risk: safe_write. It is categorised as a Write tool in the Notion MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on mission_log_decision? +

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

What risk level is mission_log_decision? +

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

Can I rate-limit mission_log_decision? +

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

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

mission_log_decision is provided by the Notion MCP server (limelight-management-group/notion-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.