AI agents invoke tla_parse 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.
This tool runs the SANY parser/analyzer tool against TLA+ source code. While it is primarily a read/analysis operation with no persistent side effects, it executes an external toolchain process (SANY) on user-supplied content. It falls into Execute rather than Read because it invokes an external program whose behavior depends on the input.
From the tool's definition Parse and syntax-check a TLA+ module using SANY (Syntactic Analyzer)
Attacks that exploit this kind of access
Parse and syntax-check a TLA+ module using SANY (Syntactic Analyzer). Returns parse errors and the list of modules parsed. 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.
Register the Tlaplus MCP server in PolicyLayer and add a rule for tla_parse: 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.
tla_parse is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the tla_parse 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.
Set action: deny in the PolicyLayer policy for tla_parse. 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.
tla_parse 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.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →