trip_history · Personal Brain MCP: Risk & Policy

WHAT IT DOES

What trip_history does on Personal Brain

AI agents use trip_history 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 trip_history needs a policy

The tool primarily performs data creation and modification (add trips, log return details) on personal travel history. While it includes a 'list' query action (Read), the presence of 'add' and 'log_return' actions makes this a Write tool overall. Severity is medium because misuse could clutter or falsify personal travel records, but the data itself is non-destructive and low-blast-radius for an AI agent.

From the tool's definition Tool supports 'add' action to create planned/past trips and 'log_return' to add highlights/rating after trips. These are reversible write operations that create or modify personal travel records.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

trip_history Rate-limited

trip_history 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": {
    "trip_history": {
      "limits": [
        {
          "counter": "trip_history_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 trip_history

What does the trip_history tool do? +

Personal travel history. action=list shows trips (filterable), add creates a planned/past trip, log_return adds highlights/rating after the trip. 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 trip_history? +

Register the Personal Brain MCP server in PolicyLayer and add a rule for trip_history: 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 trip_history? +

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

Can I rate-limit trip_history? +

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

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

trip_history 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.