// SCAN REPORT

Transaction Coordinator

11 tools. 2 can modify or destroy data without limits.

2 write tools that can modify data. Rate limits recommended.

Last updated: 6 Jun 2026

2 can modify or destroy data

9 read-only

11 tools total

Free to start. No card required.

TOOL MAP

Read (9) Write / Execute (2) Destructive / Financial (0)

CONTEXT-WINDOW COST

2,487 tokens of tool definitions, loaded on every request

1.2% of a 200k context window

418 heaviest tool: draft_motion_from_matter

Full per-tool breakdown → Model it in the token calculator →

WHAT CAN GO WRONG

Write operations (draft_motion_from_matter) modify state. Without rate limits, an agent can make hundreds of changes in seconds — faster than any human can review or revert.

Execute tools (recompute_deadlines) trigger processes with side effects. Builds, notifications, workflows — all fired without throttling.

RECOMMENDED RULES

Rate limit write operations

{
  "draft_motion_from_matter": {
    "limits": [
      {
        "counter": "draft_motion_from_matter_per_hour",
        "window": "hour",
        "max": 30,
        "scope": "grant"
      }
    ]
  }
}

Prevents bulk unintended modifications from agents caught in loops.

Cap read operations

{
  "calculate_savings": {
    "limits": [
      {
        "counter": "calculate_savings_per_minute",
        "window": "minute",
        "max": 60,
        "scope": "grant"
      }
    ]
  }
}

Controls API costs and prevents retry loops from exhausting upstream rate limits.

ALL 11 TRANSACTION COORDINATOR TOOLS

EXECUTE 1 tools

Execute recompute_deadlines

WRITE 1 tools

Write draft_motion_from_matter

READ 9 tools

Read calculate_savings Read check_motion_status Read extract_contract_from_url Read is_primacoda_right_for_me Read list_motions Read list_my_deadlines Read primacoda_info Read record_lead Read search_case_law

FAQ

How do I prevent bulk modifications through Transaction Coordinator? +

The Transaction Coordinator server has 1 write tools including draft_motion_from_matter. Set a rate limit in your policy -- for example, 10 calls per hour prevents an agent from making more than 10 modifications per hour. PolicyLayer enforces this at the gateway, before calls reach Transaction Coordinator.

How many tools does the Transaction Coordinator MCP server expose? +

11 tools across 3 categories: Execute, Read, Write. 9 are read-only. 2 can modify, create, or delete data.

How do I enforce a policy on Transaction Coordinator? +

Register the Transaction Coordinator MCP server in PolicyLayer, apply the suggested rules above (adjust the limits to your use case), and point your AI client at the PolicyLayer proxy URL instead of the server directly. Your agents keep the same tools; PolicyLayer evaluates every call against policy before it executes. Nothing to install, live in minutes.

// RELATED SERVERS

Other MCP servers with similar tools.

Starter policies for each. Same risk classification, live on your fleet in minutes.

Enforce policy on every Transaction Coordinator tool call.

Deterministic rules across all 11 Transaction Coordinator tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

SECURE TRANSACTION COORDINATOR →

Free to start. No card required.

4,600+ MCP servers and 31,000+ tools scanned and risk-classified.

Transaction Coordinator

// TOOL MAP

// CONTEXT-WINDOW COST

// WHAT CAN GO WRONG

// RECOMMENDED RULES

// ALL 11 TRANSACTION COORDINATOR TOOLS

// FAQ