sync_history · Rocket Cli MCP: Risk & Policy

WHAT IT DOES

What sync_history does on Rocket Cli

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

WHY IT NEEDS A POLICY

Why sync_history needs a policy

This tool fetches data from Rocket.Chat and writes it into the local SQLite cache. It modifies local state (the cache database) by inserting/updating records, making it a Write operation. It does not execute code, delete data, or involve financial transactions. Severity is medium because it modifies a local database, though the data is read-only message history from the server.

From the tool's definition 'Load older message history for a room into the local cache'

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

sync_history Rate-limited

sync_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": {
    "sync_history": {
      "limits": [
        {
          "counter": "sync_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 Rocket Cli, so you can run agents against it safely.

FAQ

Questions about sync_history

What does the sync_history tool do? +

Load older message history for a room into the local cache. Use. It is categorised as a Write tool in the Rocket Cli MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on sync_history? +

Register the Rocket Cli MCP server in PolicyLayer and add a rule for sync_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 Rocket Cli. Nothing to install.

What risk level is sync_history? +

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

Can I rate-limit sync_history? +

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

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

sync_history is provided by the Rocket Cli MCP server (jeanfbrito/rocket-cli). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.