log_interaction · Personal Brain MCP: Risk & Policy

WHAT IT DOES

What log_interaction does on Personal Brain

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

WHY IT NEEDS A POLICY

Why log_interaction needs a policy

This tool creates new records (interaction logs) and modifies state (follow-up dates) in a personal database, which are reversible Write operations. It does not retrieve data (Read), execute arbitrary code (Execute), irreversibly delete data (Destructive), or move money (Financial).

From the tool's definition Tool description states 'Log a touchpoint with a personal contact' and 'set a follow-up date', indicating creation and modification of contact interaction records.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

log_interaction Rate-limited

log_interaction 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": {
    "log_interaction": {
      "limits": [
        {
          "counter": "log_interaction_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 Personal Brain, so you can run agents against it safely.

FAQ

Questions about log_interaction

What does the log_interaction tool do? +

Log a touchpoint with a personal contact (text, call, in-person, etc.). Optionally set a follow-up date. It is categorised as a Write tool in the Personal Brain MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on log_interaction? +

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

What risk level is log_interaction? +

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

Can I rate-limit log_interaction? +

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

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

log_interaction is provided by the Personal Brain MCP server (phantomts/personal-brain-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.