sync_workspace_data · Chronicle MCP: Risk & Policy

WHAT IT DOES

What sync_workspace_data does on Chronicle MCP

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

WHY IT NEEDS A POLICY

Why sync_workspace_data needs a policy

The tool ingests and normalizes external data into the Chronicle memory vault. This is a write operation — it creates or modifies stored records by importing conversation data from external sources. It does not appear to delete data or execute code, though it does process raw content which slightly elevates risk.

From the tool's definition Ingest and normalize external conversations or live transcripts

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

sync_workspace_data Rate-limited

sync_workspace_data 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_workspace_data": {
      "limits": [
        {
          "counter": "sync_workspace_data_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 Chronicle MCP, so you can run agents against it safely.

FAQ

Questions about sync_workspace_data

What does the sync_workspace_data tool do? +

Ingest and normalize external conversations or live transcripts. Options for source_type: 'agent_transcripts', 'cursor_agent_transcripts', 'local_path', 'raw_content'. It is categorised as a Write tool in the Chronicle 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 sync_workspace_data? +

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

What risk level is sync_workspace_data? +

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

Can I rate-limit sync_workspace_data? +

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

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

sync_workspace_data is provided by the Chronicle MCP server (pypi:chronicle-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// THE FULL RECORD

sync_workspace_data is one line of Chronicle's registry record.

The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.

Teams ship this data inside their own products. See what a licence covers →