tlc_generate_trace_spec · Tlaplus MCP: Risk & Policy

WHAT IT DOES

What tlc_generate_trace_spec does on Tlaplus

AI agents invoke tlc_generate_trace_spec to trigger actions in Tlaplus. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.

WHY IT NEEDS A POLICY

Why tlc_generate_trace_spec needs a policy

The tool runs an external process (TLC model checker) and writes output files to disk. It spans Execute and Write; Execute is more severe and accurately describes triggering an external toolchain process whose effects depend on the input spec.

From the tool's definition 'Run TLC model-checking on a TLA+ spec with -generateSpecTE to produce a Trace Explorer spec' — this executes the TLC model checker and generates output files (SpecTE.tla / SpecTE.cfg)

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

tlc_generate_trace_spec Rate-limited

tlc_generate_trace_spec stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "tlc_generate_trace_spec": {
      "limits": [
        {
          "counter": "tlc_generate_trace_spec_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Tlaplus, so you can run agents against it safely.

FAQ

Questions about tlc_generate_trace_spec

What does the tlc_generate_trace_spec tool do? +

Run TLC model-checking on a TLA+ spec with -generateSpecTE to produce a Trace Explorer spec (SpecTE.tla / SpecTE.cfg). This is useful for debugging counter-examples: it generates a standalone spec that replays the error trace. It is categorised as a Execute tool in the Tlaplus MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on tlc_generate_trace_spec? +

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

What risk level is tlc_generate_trace_spec? +

tlc_generate_trace_spec is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit tlc_generate_trace_spec? +

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

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

tlc_generate_trace_spec is provided by the Tlaplus MCP server (richashworth/tlaplus-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.